Shell options (set -e, set -x) in Linux CLI - Time & Space Complexity

Time Complexity: Shell options (set -e, set -x)

O(n)

Understanding Time Complexity

When using shell options like set -e and set -x, it is important to understand how they affect script execution time.

We want to see how these options change the way commands run and how long the script takes as it grows.

Scenario Under Consideration

Analyze the time complexity of the following shell script snippet.

#!/bin/bash
set -e
set -x

for file in *.txt; do
  grep "pattern" "$file"
done

This script stops on errors (set -e) and prints each command before running it (set -x), looping over text files to search for a pattern.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for loop runs a grep command on each file.
• How many times: Once for each .txt file in the folder.

How Execution Grows With Input

As the number of .txt files grows, the script runs more grep commands and prints more lines due to set -x.

Input Size (n)	Approx. Operations
10	About 10 grep runs and 10 command prints
100	About 100 grep runs and 100 command prints
1000	About 1000 grep runs and 1000 command prints

Pattern observation: The number of operations grows directly with the number of files.

Final Time Complexity

Time Complexity: O(n)

This means the script's running time grows linearly with the number of files it processes.

Common Mistake

[X] Wrong: "Using set -x or set -e changes the loop's time complexity to something bigger like quadratic."

[OK] Correct: These options only add extra output or stop on errors but do not add nested loops or repeated work inside the loop, so the time still grows linearly.

Interview Connect

Understanding how shell options affect script execution helps you write reliable scripts and explain their performance clearly in real work or interviews.

Self-Check

"What if we added a nested loop inside the for loop to process each file's lines? How would the time complexity change?"

Practice

1. What does the shell option set -e do in a script?

easy

A. Stops the script immediately if any command returns an error

B. Prints each command before executing it

C. Ignores all errors and continues running

D. Runs the script in the background

Solution

1. Step 1: Understand the purpose of set -e

   This option makes the shell stop running the script if any command fails (returns a non-zero exit code).

2. Step 2: Compare with other options

   set -x prints commands, but set -e stops on errors, so stopping on error is correct.

3. Final Answer:

   Stops the script immediately if any command returns an error -> Option A

4. Quick Check:

   set -e stops on error [OK]

Hint: Remember: 'e' for error stop [OK]

Common Mistakes:

• Confusing set -e with set -x
• Thinking it ignores errors
• Assuming it runs commands silently

2. Which of the following is the correct way to enable both set -e and set -x in a shell script?

easy

A. set -x e

B. set -xe

C. set e -x

D. set -e x

Solution

1. Step 1: Understand combined options syntax

   Shell options can be combined after a single dash, order does not matter, so set -xe works.

2. Step 2: Check options with spaces

   set e -x is invalid syntax, and set -x e or set -e x set only one option.

3. Final Answer:

   set -xe -> Option B

4. Quick Check:

   Combine options after one dash [OK]

Hint: Combine flags after one dash, order doesn't matter [OK]

Common Mistakes:

• Using spaces between flags incorrectly
• Writing flags without dashes
• Assuming order matters

3. Given this script snippet with set -e enabled:

set -e
mkdir /tmp/mydir
cd /tmp/mydir
false
echo "This will not print"

What will be the output when running this script?

medium

A. Fails at mkdir and stops immediately

B. Creates directory, changes directory, prints 'This will not print'

C. Creates directory, changes directory, then stops at false; no echo output

D. Runs all commands including echo

Solution

1. Step 1: Trace commands with set -e

   The script creates /tmp/mydir, changes into it, then runs false which returns error (non-zero).

2. Step 2: Effect of set -e on error

   Because set -e stops on any error, the script stops after false and does not run the echo command.

3. Final Answer:

   Creates directory, changes directory, then stops at false; no echo output -> Option C

4. Quick Check:

   set -e stops script on error [OK]

Hint: Remember: script stops at first error with set -e [OK]

Common Mistakes:

• Assuming echo runs after error
• Thinking mkdir fails by default
• Ignoring effect of set -e

4. You have this script:

#!/bin/bash
set -x
ls /nonexistent
pwd

What is the problem and how to fix it so the script continues after the error?

medium

A. No problem; script runs all commands

B. Problem: script stops on error; fix by removing set -x

C. Problem: script prints commands; fix by removing set -x

D. Problem: script stops on error; fix by removing set -e (not set here)

Solution

1. Step 1: Analyze script options

   The script uses set -x which prints commands but does not stop on errors. There is no set -e so script continues despite ls error and runs pwd.

2. Step 2: Identify problem and fix

   Script already continues after error since no set -e. No problem exists.

3. Final Answer:

   No problem; script runs all commands -> Option A

4. Quick Check:

   set -x prints commands, set -e stops on error [OK]

Hint: Remember: set -x prints, set -e stops [OK]

Common Mistakes:

• Confusing set -x with set -e
• Assuming set -x stops script
• Ignoring missing set -e

5. You want to debug a script that sometimes fails silently. Which combination of shell options helps you see each command as it runs and stops immediately on errors?

hard

A. set -e only

B. set -x e

C. set -x only

D. set -ex

Solution

1. Step 1: Understand debugging needs

   To debug, you want to see commands as they run (set -x) and stop on errors (set -e).

2. Step 2: Combine options correctly

   set -ex enables both correctly.

3. Final Answer:

   set -ex -> Option D

4. Quick Check:

   Show commands and stop on error = set -ex [OK]

Hint: Use both -e and -x together to debug safely [OK]

Common Mistakes:

• Using only one option and missing the other
• Thinking order matters strictly
• Confusing which option stops or prints