Exit codes ($?) in Bash Scripting - Time & Space Complexity

Time Complexity: Exit codes ($?)

O(n)

Understanding Time Complexity

We want to understand how checking exit codes affects the time a script takes to run.

Specifically, how does the number of commands impact the time spent checking their exit codes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

for file in *.txt; do
  cp "$file" /backup/
  if [ $? -ne 0 ]; then
    echo "Copy failed for $file"
  fi
done
    

This script copies all .txt files to a backup folder and checks the exit code after each copy to see if it succeeded.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for loop that goes through each .txt file.
• How many times: Once for each .txt file in the folder.
• The exit code check [ $? -ne 0 ] runs once per file, right after the copy command.

How Execution Grows With Input

As the number of .txt files grows, the script runs the copy and exit code check for each file.

Input Size (n)	Approx. Operations
10	About 10 copies and 10 exit code checks
100	About 100 copies and 100 exit code checks
1000	About 1000 copies and 1000 exit code checks

Pattern observation: The total work grows directly with the number of files. Double the files, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows linearly with the number of files processed.

Common Mistake

[X] Wrong: "Checking the exit code is a separate step that doesn't add to the time complexity."

[OK] Correct: The exit code check runs every time inside the loop, so it adds work proportional to the number of files, affecting total time.

Interview Connect

Understanding how simple checks like exit codes add to script runtime helps you write efficient scripts and explain your reasoning clearly in interviews.

Self-Check

What if we removed the exit code check inside the loop? How would the time complexity change?

Practice

1. What does the exit code 0 usually mean in bash scripting?

easy

A. The command is still running

B. The command failed

C. The command was skipped

D. The command was successful

Solution

1. Step 1: Understand exit codes meaning

   In bash, exit code 0 means success, any other number means failure or error.

2. Step 2: Interpret exit code 0

   Since 0 means success, the command completed without errors.

3. Final Answer:

   The command was successful -> Option D

4. Quick Check:

   Exit code 0 = success [OK]

Hint: Exit code 0 means success, anything else means error [OK]

Common Mistakes:

• Thinking 0 means failure
• Confusing exit code with process ID
• Checking $? too late after command

2. Which of the following is the correct way to check the exit code of the last command in bash?

easy

A. echo $exit_code

B. echo $?

C. echo $lastcode

D. echo $status

Solution

1. Step 1: Recall special variable for exit code

   The special variable $? holds the exit code of the last command.

2. Step 2: Verify correct syntax

   Using echo $? prints the exit code correctly.

3. Final Answer:

   echo $? -> Option B

4. Quick Check:

   Use $? to get last exit code [OK]

Hint: Use $? immediately after command to get exit code [OK]

Common Mistakes:

• Using undefined variables like $exit_code
• Forgetting to check $? right after command
• Using $status which is not standard

3. What will be the output of this script?

ls /nonexistent_dir
 echo $?

medium

A. 2

B. 0

C. No output

D. ls: cannot access '/nonexistent_dir': No such file or directory

Solution

1. Step 1: Understand the command behavior

   The command ls /nonexistent_dir tries to list a folder that does not exist, so it fails.

2. Step 2: Check exit code after failure

   After failure, $? holds a non-zero exit code, 2 for ls missing directories.

3. Final Answer:

   2 -> Option A

4. Quick Check:

   Failed command exit code ≠ 0 [OK]

Hint: Failed commands return non-zero exit codes like 2 [OK]

Common Mistakes:

• Assuming output is 0 for failure
• Confusing error message with exit code
• Expecting no output from echo

4. Consider this script snippet:

mkdir test_dir
false
if [ $? -eq 0 ]; then
  echo "Created"
else
  echo "Failed"
fi

What is the problem if the script always prints "Failed" even when the directory is created?

medium

A. mkdir command does not set exit code

B. The syntax of if statement is wrong

C. The $? is checked too late after mkdir

D. echo command overwrites the exit code

Solution

1. Step 1: Understand exit code timing

   The exit code $? must be checked immediately after the command it relates to.

2. Step 2: Identify delay in checking exit code

   If any command runs between mkdir and checking $?, the exit code changes.

3. Final Answer:

   The $? is checked too late after mkdir -> Option C

4. Quick Check:

   Check $? immediately after command [OK]

Hint: Check $? right after command, no commands in between [OK]

Common Mistakes:

• Checking $? after other commands
• Assuming mkdir never fails
• Misunderstanding if syntax

5. You want to run two commands in a script: cmd1 and cmd2. You want to run cmd2 only if cmd1 succeeded (exit code 0). Which is the best way to do this?

hard

A. cmd1 && cmd2

B. cmd1 || cmd2

C. cmd1; if [ $status -eq 0 ]; then cmd2; fi

D. if [ cmd1 ]; then cmd2; fi

Solution

1. Step 1: Understand conditional execution operators

   The operator && runs the second command only if the first succeeds (exit code 0).

2. Step 2: Compare options for best practice

   cmd1 && cmd2 uses cmd1 && cmd2 which is concise and reliable for this purpose.

3. Final Answer:

   cmd1 && cmd2 -> Option A

4. Quick Check:

   Use && to run second command only if first succeeds [OK]

Hint: Use && to run next command only if previous succeeds [OK]

Common Mistakes:

• Using || which runs second if first fails
• Checking $? manually when && is simpler
• Using if with command but less concise