Book Image

The Software Developer's Guide to Linux

By : David Cohen, Christian Sturm
5 (2)
Book Image

The Software Developer's Guide to Linux

5 (2)
By: David Cohen, Christian Sturm

Overview of this book

Developers are always looking to raise their game to the next level, yet most are completely lost when it comes to the Linux command line. This book is the bridge that will take you to the next level in your software development career. Most of the skills in the book can be immediately put to work to make you a more efficient developer. It’s written specifically for software engineers, not Linux system administrators, so each chapter will equip you with just enough theory to understand what you’re doing before diving into practical commands that you can use in your day-to-day work as a software developer. As you work through the book, you’ll quickly absorb the basics of how Linux works while you get comfortable moving around the command line. Once you’ve got the core skills, you’ll see how to apply them in different contexts that you’ll come across as a software developer: building and working with Docker images, automating boring build tasks with shell scripts, and troubleshooting issues in production environments. By the end of the book, you’ll be able to use Linux and the command line comfortably and apply your newfound skills in your day-to-day work to save time, troubleshoot issues, and be the command-line wizard that your team turns to.
Table of Contents (20 chapters)
18
Other Books You May Enjoy
19
Index

Output redirection: >

We want to redirect STDOUT (file descriptor 1) to a file instead of a terminal, logging the output of each command instead of printing it out to the terminal in real-time.

# bash < commands.txt > output.log

Notice that there is no visible output in the terminal now – because the > character has redirected output to output.log. Use cat to print out the logfile and confirm that it contains the expected output:

# cat output.log
/tmp/gopsinspect
hello there, friends
/bin/bash
/tmp

Use >> to append output, without overwriting

In the previous example, we created a logfile by redirecting command output with >. If you run the example a few times, you’ll notice that the logfile doesn’t grow at all. Each time you redirect output to a file with > filename, anything in that file will be overwritten.

To avoid that – as in the case of a long-lived logfile that collects output from more than a single process or command &...