Input, Output, and Redirection

# CHAPTER 9

Input, Output, and Redirection #

1. Introduction #

2. Learning Objectives #

• Define the three standard data streams: Standard Input (0), Standard Output (1), and Standard Error (2).

• Redirect standard output to permanently overwrite or append text files (> and >>).

• Segregate and redirect error messages into dedicated error log files using 2>.

• Suppress unwanted terminal output by redirecting data into /dev/null.

• Chain multiple discrete commands into a single data-processing workflow using the Pipe (|) operator.

3. The Three Standard Streams #

1. 1. stdin (Standard Input - Channel 0): The data flowing INTO the program (e.g., typing on the keyboard).

1. 2. stdout (Standard Output - Channel 1): The normal, successful text flowing OUT of the program.

1. 3. stderr (Standard Error - Channel 2): The error and failure messages flowing OUT of the program.

4. Output Redirection (> and >>) #

1. Overwrite (>):

# The output of echo goes IN to the text file.
# WARNING: If the file already exists, it is instantly ERASED and overwritten!
echo "Deployment successful." > report.txt

2. Append (>>): In administrative scripting, you usually want to maintain a continuous history log. You use double arrows to *append* data to the absolute bottom of the file, safely preserving the older data.

echo "Server Rebooted." >> history.log
echo "Database Started." >> history.log

5. Error Redirection (2>) #

# Redirect ONLY the errors into an error log
ls /fake_dir 2> errors.txt

# Pro-Tip: Merge both streams! Send Channel 2 to the exact same place as Channel 1
# (This is standard practice for cron job logging)
./my_script.sh > full_output.log 2>&1

6. The Black Hole (/dev/null) #

# Search the entire hard drive for a file, but throw all the "Permission Denied" errors into the trash
find / -name "secret.txt" 2> /dev/null

7. The Pipe Operator (|) #

# Grab the massive output of all running processes, and PIPE it into 'grep' to only show SSH
ps aux | grep "sshd"

# Read a 50,000 line log file, and PIPE it into 'tail' to only view the bottom 5 lines
cat /var/log/syslog | tail -n 5

8. Diagrams/Visual Suggestions #

• A Blue pipe labeled stdout (1). Show it utilizing a > valve to dump water into a file icon labeled log.txt.

• A Red pipe labeled stderr (2). Show it utilizing a 2> valve to dump red water into a trash can icon labeled /dev/null.

9. Best Practices #

• Never > in Production Logs: The single most destructive typo an administrator can make is using > instead of >> when targeting a production log file. Typing echo "Event" > apache.log instantly annihilates years of forensic web server history. Train your fingers to default to >> appending.

10. Common Mistakes #

• Syntax Order Matters (2>&1): When combining streams, the order of redirection is strictly enforced by the shell. You must type command > log.txt 2>&1. If you type command 2>&1 > log.txt, it will fail because you attempted to redirect channel 2 into channel 1 *before* channel 1 was actually pointing at the text file.

11. Mini Project: The Silent Connectivity Logger #

1. 1. nano net_monitor.sh

1. 2. Write the code:

#!/bin/sh

LOG_FILE="/tmp/network_drops.log"

echo "Running network diagnostic (Silent Mode)..."

# Ping Google once. We do not care about the text output, so we dump stdout to the black hole.
# We also dump stderr to the black hole just in case.
ping -c 1 8.8.8.8 > /dev/null 2>&1

# Check the exit code of the ping command
if [ $? -ne 0 ]; then
    # It failed! Append a timestamp to the error log.
    CURRENT_TIME=$(date +"%Y-%m-%d %H:%M:%S")
    echo "[$CURRENT_TIME] CRITICAL: Network connection failed!" >> "$LOG_FILE"
    echo "Network failure detected and logged."
else
    echo "Network is healthy. No logs created."
fi

1. 3. Run it. You have built an automated diagnostic tool that intelligently manages its own data streams.

12. Practice Exercises #

1. 1. Contrast the mechanical operation of the > operator versus the >> operator. In what specific administrative scenario would utilizing > cause catastrophic data loss?

1. 2. Explain the fundamental purpose of the /dev/null file within the Unix architecture. Provide a practical scripting example demonstrating its utility.

13. MCQs with Answers #

14. Interview Questions #

• Q: A developer brings you a shell script containing the execution line ./deploydatabase.sh > deployment.log 2>&1. Explain in precise technical detail exactly what the 2>&1 syntax is accomplishing regarding Linux data streams.

• Q: Walk me through the exact terminal syntax required to execute a highly verbose compilation script named build.sh, safely discard all normal standard operational output, but capture all critical compilation errors into a file named buildfailures.log.

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #