stderr redirection (2>, 2>>) in Linux CLI - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this command?

Consider the command:

ls /nonexistent 2> error.log; cat error.log

What will be the output of cat error.log?

Linux CLI

ls /nonexistent 2> error.log; cat error.log

A ls: cannot access '/nonexistent': No such file or directory

B bash: ls: command not found

C

ls: cannot access '/nonexistent': No such file or directory
ls: cannot access '/nonexistent': No such file or directory

D No output (empty file)

💡 Hint

The 2> operator redirects error messages to a file.

The command tries to list a non-existing directory. The error message is redirected to 'error.log'. Using 'cat error.log' shows the error message inside the file.

💻 Command Output

intermediate

What happens when appending stderr with 2>>?

Given the commands:

echo 'First error' 1>&2 2> error.log
 echo 'Second error' 1>&2 2>> error.log
 cat error.log

What will be the output of cat error.log?

Linux CLI

echo 'First error' 1>&2 2> error.log
 echo 'Second error' 1>&2 2>> error.log
 cat error.log

A Second error

B No output

C First error

D

First error
Second error

💡 Hint

2> overwrites, 2>> appends to the file.

The first echo sends 'First error' to stderr, redirected to error.log (overwrites). The second echo appends 'Second error' to error.log. So both lines appear in the file.

🔧 Debug

advanced

Why does this command not redirect stderr as expected?

You run:

grep 'pattern' file.txt | wc -l 2> errors.log

But errors.log remains empty even if file.txt does not exist. Why?

Linux CLI

grep 'pattern' file.txt | wc -l 2> errors.log

A Because wc -l overwrites errors.log

B Because 2> redirects stderr of wc, not grep

C Because file.txt exists and has no errors

D Because only stdout of grep is piped, stderr is not redirected properly

💡 Hint

Think about which command's stderr is redirected.

In shell pipelines, a redirection like 2> after a pipe applies to the preceding command (wc -l here), not the first command (grep). Grep's stderr goes to the terminal, and wc -l produces no stderr, leaving errors.log empty.

📝 Syntax

advanced

Which command correctly appends stderr to a file?

Choose the command that appends stderr output to errors.log without overwriting it.

A command 2>> errors.log

B command 2> errors.log

C command >> 2 errors.log

D command 2> > errors.log

💡 Hint

Appending means adding to the end of the file.

2>> appends stderr to the file. 2> overwrites. The other options are invalid syntax.

🚀 Application

expert

How to redirect both stdout and stderr to different files simultaneously?

You want to run mycommand and save its standard output to out.log and its error output to err.log. Which command does this correctly?

A mycommand > out.log 2>> err.log

B mycommand 2> err.log > out.log

C mycommand > out.log 2> err.log

D mycommand 2>> err.log > out.log

💡 Hint

Order of redirections matters less here, but appending vs overwriting does.

Both A and B redirect stdout and stderr to separate files correctly. However, the order does not affect the result here. Options C and D append stderr instead of overwriting. The question asks for saving outputs, not appending. So A is the best answer.

Practice

1. What does the command ls nonexistingfile 2> error.log do in Linux?

easy

A. Sends the error message to the file error.log, replacing its content.

B. Appends the error message to the file error.log.

C. Sends the normal output to error.log.

D. Displays the error message on the screen only.

Solution

1. Step 1: Understand 2> redirection

   The operator 2> redirects standard error (stderr) to a file, replacing its content.

2. Step 2: Analyze the command behavior

   The command tries to list a non-existing file, so it produces an error message sent to error.log, overwriting previous content.

3. Final Answer:

   Sends the error message to the file error.log, replacing its content. -> Option A

4. Quick Check:

   2> replaces error file content [OK]

Hint: 2> overwrites error file, 2>> appends error [OK]

Common Mistakes:

• Confusing 2> with 2>>
• Thinking 2> sends normal output
• Assuming error shows on screen

2. Which of the following is the correct syntax to append error messages to a file named errors.txt?

easy

A. command 2>> errors.txt

B. command 2> errors.txt

C. command >2 errors.txt

D. command >>2 errors.txt

Solution

1. Step 1: Identify append operator for stderr

   The operator 2>> appends standard error to a file without overwriting it.

2. Step 2: Match syntax with options

   command 2>> errors.txt uses 2>> correctly to append errors to errors.txt.

3. Final Answer:

   command 2>> errors.txt -> Option A

4. Quick Check:

   Append errors with 2>> [OK]

Hint: Use 2>> to add errors, not overwrite [OK]

Common Mistakes:

• Using 2> instead of 2>> to append
• Swapping > and 2 in syntax
• Using >>2 which is invalid

3. What will be the content of log.txt after running this command twice?

grep 'pattern' file.txt 2>> log.txt

Assuming file.txt does not exist.

medium

A. log.txt will be empty because errors go to screen.

B. log.txt will contain only one error message, overwritten by second run.

C. log.txt will contain two copies of the error message appended.

D. log.txt will contain normal grep output twice.

Solution

1. Step 1: Understand 2>> appends stderr

   The operator 2>> appends error messages to the file without deleting previous content.

2. Step 2: Analyze repeated command effect

   Since file.txt is missing, grep outputs an error each time, appending twice to log.txt.

3. Final Answer:

   log.txt will contain two copies of the error message appended. -> Option C

4. Quick Check:

   2>> appends errors, so two runs add two messages [OK]

Hint: 2>> adds errors, so repeated runs append messages [OK]

Common Mistakes:

• Thinking 2>> overwrites file
• Assuming errors print on screen
• Confusing normal output with error output

4. You run cat missingfile 2> errors.log but errors.log remains empty. What is the likely mistake?

medium

A. You redirected stdout instead of stderr.

B. The command ran successfully with no errors.

C. You used 2>> instead of 2>.

D. The file missingfile actually exists.

Solution

1. Step 1: Check if error occurs

   If missingfile exists, cat produces no error, so nothing is sent to errors.log.

2. Step 2: Understand empty error file

   Since no error happened, the error file remains empty despite redirection.

3. Final Answer:

   The command ran successfully with no errors. -> Option B

4. Quick Check:

   No error means empty error file [OK]

Hint: Empty error file means no error occurred [OK]

Common Mistakes:

• Assuming 2>>> is valid syntax
• Confusing stdout and stderr redirection
• Ignoring that file might exist

5. You want to run a script that logs all error messages to error.log without losing previous errors, but normal output should show on screen. Which command correctly does this?

hard

A. ./script.sh >> error.log 2>> error.log

B. ./script.sh 2> error.log

C. ./script.sh > error.log 2>&1

D. ./script.sh 2>> error.log

Solution

1. Step 1: Identify error logging without overwrite

   To keep previous errors, use 2>> to append stderr to error.log.

2. Step 2: Ensure normal output shows on screen

   Redirecting only stderr leaves stdout on screen, so ./script.sh 2>> error.log fits requirements.

3. Final Answer:

   ./script.sh 2>> error.log -> Option D

4. Quick Check:

   Append errors with 2>>; stdout stays on screen [OK]

Hint: Use 2>> for errors, no stdout redirection to keep screen output [OK]

Common Mistakes:

• Using 2> which overwrites error log
• Redirecting stdout to file losing screen output
• Combining stdout and stderr incorrectly