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

Error redirection with 2>

Many command-line programs that have a lot of expected output will also output occasional (expected) errors – think of a find command that encounters occasional ‘permission denied’ errors for directories you’re not allowed to peek inside.

Although these kinds of errors are minor and expected, you don’t want them mixed in with everything else, polluting your output. This becomes especially important when you’re not using command-line tools interactively, but rather writing small scripts or larger programs that process the output of the commands you’re running.

You’ve seen how to redirect Standard Input (fd 0) and Standard Output (fd 1). Let’s look at how to redirect Standard Error (fd 2) using the 2> (redirect file descriptor 2) syntax.

find /etc/ -name php.ini > /tmp/phpinis.log 2>/dev/null

This command searches for any files named php.ini inside the /etc directory tree. The files it...