Running commands in background (&) in Bash Scripting - Time & Space Complexity

Time Complexity: Running commands in background (&)

O(1)

Understanding Time Complexity

When we run commands in the background using &, we want to know how this affects the total time our script takes.

We ask: How does running tasks in the background change the time needed as we add more commands?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

for i in {1..n}; do
  sleep 1 &
done
wait
    

This script starts n sleep commands in the background, each pausing for 1 second, then waits for all to finish.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Starting n background sleep commands.
• How many times: The loop runs n times, launching all commands almost instantly.

How Execution Grows With Input

Even though we start n commands, they run at the same time.

Input Size (n)	Approx. Operations
10	About 1 second total
100	About 1 second total
1000	About 1 second total

Pattern observation: Total time stays roughly the same no matter how many commands run in background.

Final Time Complexity

Time Complexity: O(1)

This means the total time does not grow with more commands because they run at the same time.

Common Mistake

[X] Wrong: "Running more background commands always takes more total time."

[OK] Correct: Since commands run simultaneously, total time depends on the longest single command, not the number of commands.

Interview Connect

Understanding how background tasks affect time helps you write scripts that save time and run efficiently, a useful skill in many real-world tasks.

Self-Check

What if the commands run in background have different durations? How would the total time change?

Practice

1. What does adding & at the end of a command in bash do?

easy

A. Runs the command in the background, freeing the terminal immediately

B. Stops the command from running

C. Runs the command with higher priority

D. Runs the command only if another command fails

Solution

1. Step 1: Understand the role of & in bash

   The & symbol placed after a command tells bash to run that command in the background.

2. Step 2: Effect on terminal usability

   Running a command in the background frees the terminal immediately so you can type new commands without waiting.

3. Final Answer:

   Runs the command in the background, freeing the terminal immediately -> Option A

4. Quick Check:

   Background run = frees terminal [OK]

Hint: Remember: & means run in background and free terminal [OK]

Common Mistakes:

• Thinking & stops the command
• Confusing & with command priority
• Assuming & waits for command to finish

2. Which of the following is the correct syntax to run sleep 10 in the background?

easy

A. sleep 10 &&

B. sleep 10 &

C. sleep & 10

D. & sleep 10

Solution

1. Step 1: Identify correct placement of &

   The & must come immediately after the full command to run it in the background.

2. Step 2: Check each option

   sleep 10 & places & correctly after sleep 10. The other options misuse & or use wrong symbols.

3. Final Answer:

   sleep 10 & -> Option B

4. Quick Check:

   Command & = correct syntax [OK]

Hint: Put & at the end of the command line [OK]

Common Mistakes:

• Placing & before the command
• Inserting & between command and arguments
• Using && instead of &

3. What will be the output of the following commands?

echo "Start"
sleep 3 &
echo "End"

medium

A. Only Start is printed

B. Start\n(wait 3 seconds)\nEnd

C. Start\nEnd (immediately), then sleep runs silently

D. Start\nEnd\nError message

Solution

1. Step 1: Analyze command order and background execution

   The sleep 3 & runs in the background, so it does not block the terminal.

2. Step 2: Understand output timing

   "Start" prints first, then sleep 3 & starts silently in background, then "End" prints immediately.

3. Final Answer:

   Start\nEnd (immediately), then sleep runs silently -> Option C

4. Quick Check:

   Background sleep = immediate End print [OK]

Hint: Background commands don't block output [OK]

Common Mistakes:

• Expecting sleep to delay 'End' output
• Thinking background commands print output
• Confusing & with && causing wait

4. Identify the error in this script snippet:

echo "Start"
sleep 5 &
wait
wait
 echo "Done"

medium

A. The echo command should be before wait

B. Using two wait commands causes an error

C. Missing & after sleep 5

D. The second wait is redundant but not an error

Solution

1. Step 1: Understand wait behavior

   The wait command waits for all background jobs to finish. Multiple wait commands do not cause errors but the second is unnecessary.

2. Step 2: Check script correctness

   The script runs sleep 5 in background, waits twice, then prints "Done". This works but the second wait is redundant.

3. Final Answer:

   The second wait is redundant but not an error -> Option D

4. Quick Check:

   Multiple waits allowed, redundant but no error [OK]

Hint: Multiple waits don't error, just wait again [OK]

Common Mistakes:

• Thinking multiple waits cause errors
• Forgetting & after sleep
• Misplacing echo before wait

5. You want to run three commands cmd1, cmd2, and cmd3 in the background simultaneously, then wait for all to finish before printing "All done". Which script correctly does this?

hard

A. cmd1 &
cmd2 &
cmd3 &
wait
echo "All done"

B. cmd1 & cmd2 & cmd3 & wait &
echo "All done"

C. cmd1 & cmd2 & cmd3
echo "All done"

D. cmd1 & cmd2 & cmd3 &
echo "All done"

Solution

1. Step 1: Run each command in background separately

   Each command must end with & to run in background independently.

2. Step 2: Use wait to pause until all background jobs finish

   After starting all commands, wait pauses script until all finish, then prints "All done".

3. Final Answer:

   cmd1 & cmd2 & cmd3 & wait echo "All done" -> Option A

4. Quick Check:

   Separate & + wait before echo = correct [OK]

Hint: Put & after each command, then wait once [OK]

Common Mistakes:

• Running all commands on one line without separate &
• Omitting wait causing early echo
• Placing echo on same line as background commands