📖 Scenario: You are managing a server where you need to run multiple tasks without waiting for each to finish before starting the next. Running commands in the background helps you do this efficiently.
🎯 Goal: Learn how to run commands in the background using & so you can start a task and continue working without waiting for it to finish.
📋 What You'll Learn
Create a simple command that runs in the foreground
Add a background command using &
Use a variable to hold a command string
Run the command stored in the variable in the background
Print a message after starting the background command
💡 Why This Matters
🌍 Real World
Running commands in the background is useful when you want to start long tasks but keep using the terminal for other work.
💼 Career
System administrators and developers often run scripts and commands in the background to improve productivity and manage multiple tasks efficiently.
Progress0 / 4 steps
1
Create a simple command
Write a command that uses echo to display the text "Starting task".
Bash Scripting
Hint
Use echo "Starting task" to print the message.
2
Run a command in the background
Add a command that runs sleep 5 in the background using & so it does not block the terminal.
Bash Scripting
Hint
Add & after sleep 5 to run it in the background.
3
Use a variable to hold a command
Create a variable called cmd and assign it the string "sleep 3". Then run the command stored in cmd in the background using &.
Bash Scripting
Hint
Assign cmd="sleep 3" and run it with $cmd &.
4
Print a message after starting background commands
Add a command to print "Tasks started" after starting the background commands.
Bash Scripting
Hint
Use echo "Tasks started" to print the message.
Practice
(1/5)
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
Step 1: Understand the role of & in bash
The & symbol placed after a command tells bash to run that command in the background.
Step 2: Effect on terminal usability
Running a command in the background frees the terminal immediately so you can type new commands without waiting.
Final Answer:
Runs the command in the background, freeing the terminal immediately -> Option A
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
Step 1: Identify correct placement of &
The & must come immediately after the full command to run it in the background.
Step 2: Check each option
sleep 10 & places & correctly after sleep 10. The other options misuse & or use wrong symbols.
Final Answer:
sleep 10 & -> Option B
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
Step 1: Analyze command order and background execution
The sleep 3 & runs in the background, so it does not block the terminal.
Step 2: Understand output timing
"Start" prints first, then sleep 3 & starts silently in background, then "End" prints immediately.
Final Answer:
Start\nEnd (immediately), then sleep runs silently -> Option C
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
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.
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.
Final Answer:
The second wait is redundant but not an error -> Option D
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
Step 1: Run each command in background separately
Each command must end with & to run in background independently.
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".
Final Answer:
cmd1 &
cmd2 &
cmd3 &
wait
echo "All done" -> Option A
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
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.