Running commands in background (&) in Bash Scripting - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this background command?

Consider the following bash command run in a terminal:

sleep 2 & echo "Done"

What will be printed immediately after running this command?

Bash Scripting

sleep 2 & echo "Done"

A Done

B No output until 2 seconds pass

C Done\nsleep 2

D sleep: command not found

💡 Hint

The ampersand (&) runs the first command in the background, so the next command runs immediately.

The command 'sleep 2 &' runs sleep in the background, so the shell immediately runs 'echo "Done"' which prints 'Done'.

💻 Command Output

intermediate

What happens if you run multiple background commands?

What will be the output of this script?

echo Start
sleep 1 &
sleep 2 &
echo End

Choose the correct output order.

Bash Scripting

echo Start
sleep 1 &
sleep 2 &
echo End

A Start\nEnd\n(sleep 1 and sleep 2 outputs)

B Start\nEnd

C Start\nsleep 1\nsleep 2\nEnd

D End\nStart

💡 Hint

Background commands do not produce output unless they have their own output commands.

Only 'echo' commands produce output here. 'sleep' commands run silently in background. So output is 'Start' then 'End'.

🔧 Debug

advanced

Why does this background command fail to run?

Look at this command:

my_script.sh &

It gives an error: 'my_script.sh: command not found'. Why?

Bash Scripting

my_script.sh &

A Background commands cannot run scripts

B The ampersand (&) is misplaced and causes syntax error

C The script is not executable or not in PATH

D The shell does not support background commands

💡 Hint

Check if the script file has execute permission and is in the current directory or PATH.

The error means the shell cannot find 'my_script.sh' as a command. Usually because it's not executable or not in PATH.

🚀 Application

advanced

How to run a command in background and save its output to a file?

You want to run long_task.sh in background and save its output to output.log. Which command does this correctly?

A long_task.sh & > output.log

B long_task.sh & output.log >

C long_task.sh &> output.log &

D long_task.sh > output.log &

💡 Hint

Redirect output before the ampersand to capture it.

Redirecting output with > before & sends output to file while running command in background.

🧠 Conceptual

expert

What is the effect of running a pipeline with background (&)?

Consider this command:

cat file.txt | grep 'hello' &

What happens when you run it?

A The whole pipeline runs in background, output goes to terminal

B Only 'grep' runs in background, 'cat' runs in foreground

C Syntax error because & cannot be used with pipelines

D The pipeline runs in background, output is discarded

💡 Hint

The ampersand puts the entire pipeline in background.

The & at the end runs the entire pipeline in background. Output still goes to terminal unless redirected.

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