Custom exit codes (exit N) in Bash Scripting - Time & Space Complexity

Time Complexity: Custom exit codes (exit N)

O(1)

Understanding Time Complexity

When using custom exit codes in bash scripts, it's important to understand how the script's running time changes as it executes commands.

We want to see how the script's steps grow when it uses exit codes to stop early or continue.

Scenario Under Consideration

Analyze the time complexity of the following bash script using custom exit codes.

#!/bin/bash
for i in {1..n}; do
  if [[ $i -eq 5 ]]; then
    exit 3  # Custom exit code
  fi
  echo "Processing $i"
done

This script loops from 1 to n, prints each number, but exits early with code 3 when i equals 5.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop iterating from 1 to n.
• How many times: Up to 5 times because the script exits early at i=5.

How Execution Grows With Input

Because the script stops at i=5, the number of steps does not grow with n beyond 5.

Input Size (n)	Approx. Operations
10	5 (stops early)
100	5 (stops early)
1000	5 (stops early)

Pattern observation: The script runs a fixed number of steps regardless of input size because of the early exit.

Final Time Complexity

Time Complexity: O(1)

This means the script runs a constant number of steps no matter how big n is, due to the early exit.

Common Mistake

[X] Wrong: "The script always runs n times because the loop goes from 1 to n."

[OK] Correct: The script stops early at i=5 using exit, so it does not complete all n iterations.

Interview Connect

Understanding how early exits affect script runtime helps you reason about efficiency and control flow in real scripts.

Self-Check

What if the exit condition was changed to i equals n instead of 5? How would the time complexity change?

Practice

1. What does the command exit 0 mean in a bash script?

easy

A. The script will continue running after this command.

B. The script encountered an error and stopped.

C. The script finished successfully without errors.

D. The script restarts from the beginning.

Solution

1. Step 1: Understand exit codes in bash

   In bash, exit 0 means the script ended without any errors.

2. Step 2: Interpret the meaning of 0

   Exit code 0 always signals success to the system or calling program.

3. Final Answer:

   The script finished successfully without errors. -> Option C

4. Quick Check:

   exit 0 = success [OK]

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

Common Mistakes:

• Thinking exit 0 means error
• Assuming script continues after exit
• Confusing exit 0 with restart

2. Which of the following is the correct syntax to exit a bash script with code 5?

easy

A. exit 5

B. exit code 5

C. exit(5)

D. exit -5

Solution

1. Step 1: Recall bash exit syntax

   The correct way to exit with a code is exit N, where N is a number.

2. Step 2: Check each option

   exit 5 uses exit 5, which is valid syntax. Others are invalid in bash.

3. Final Answer:

   exit 5 -> Option A

4. Quick Check:

   exit N syntax = exit 5 [OK]

Hint: Use just 'exit' followed by a number, no extra words [OK]

Common Mistakes:

• Adding 'code' after exit
• Using parentheses like a function
• Using negative numbers for exit

3. What will be the exit code of this script?

#!/bin/bash
if [ -f "/tmp/file.txt" ]; then
  exit 3
else
  exit 0
fi

medium

A. 0 if /tmp/file.txt exists, 3 if not

B. 3 if /tmp/file.txt exists, 0 if not

C. Always 0

D. Always 3

Solution

1. Step 1: Understand the if condition

   The script checks if the file /tmp/file.txt exists using -f.

2. Step 2: Analyze exit codes for each case

   If the file exists, it exits with code 3; otherwise, it exits with 0.

3. Final Answer:

   3 if /tmp/file.txt exists, 0 if not -> Option B

4. Quick Check:

   File exists -> exit 3; else -> exit 0 [OK]

Hint: Match exit code to condition true/false carefully [OK]

Common Mistakes:

• Mixing up the if and else branches
• Assuming exit 0 always means file exists
• Ignoring the file check condition

4. Identify the error in this script snippet:

#!/bin/bash
exit 256

medium

A. Exit code 256 is invalid; exit codes must be 0-255.

B. Missing quotes around 256.

C. exit command should be lowercase.

D. exit requires a string, not a number.

Solution

1. Step 1: Check valid exit code range

   Bash exit codes must be between 0 and 255 inclusive.

2. Step 2: Analyze the given exit code

   256 is outside this range, so it is invalid and will wrap around or cause unexpected behavior.

3. Final Answer:

   Exit code 256 is invalid; exit codes must be 0-255. -> Option A

4. Quick Check:

   Exit codes range 0-255 [OK]

Hint: Exit codes must be 0-255, no higher numbers [OK]

Common Mistakes:

• Using numbers above 255
• Thinking quotes are needed
• Confusing case sensitivity of exit

5. You want a script to exit with code 10 if a user is not root, and 0 if root. Which snippet correctly implements this?

hard

A. if [ "$USER" != "root" ]; then exit 10; else exit 0; fi

B. if [ "$UID" -eq 0 ]; then exit 10; else exit 0; fi

C. if [ "$USER" == "root" ]; then exit 10; else exit 0; fi

D. if [ "$UID" -ne 0 ]; then exit 10; else exit 0; fi

Solution

1. Step 1: Identify how to check root user

   Root user has UID 0, so checking $UID -ne 0 means user is not root.

2. Step 2: Match exit codes to condition

   If user is not root, exit 10; else exit 0 for root user.

3. Final Answer:

   if [ "$UID" -ne 0 ]; then exit 10; else exit 0; fi -> Option D

4. Quick Check:

   UID 0 means root; non-zero means not root [OK]

Hint: Use UID 0 to check root, not USER string [OK]

Common Mistakes:

• Comparing USER string instead of UID
• Reversing the exit codes
• Using == instead of -eq for numbers