wait for background processes in Bash Scripting - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to wait for all background processes to finish before continuing.

Bash Scripting

echo "Start"; sleep 2 & sleep 3 & [1]; echo "Done"

Drag options to blanks, or click blank then click option'

Aexit

Bsleep

Cwait

Dkill

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sleep' instead of 'wait' does not wait for background jobs.

Using 'kill' or 'exit' will stop the script or processes incorrectly.

The 'wait' command pauses the script until all background jobs finish.

2fill in blank

medium

Complete the code to wait for a specific background process using its process ID.

Bash Scripting

sleep 5 & pid=$!; echo "Waiting for process"; [1] $pid; echo "Process done"

Drag options to blanks, or click blank then click option'

Await

Bsleep

Ckill

Djobs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'kill' will terminate the process instead of waiting.

Using 'jobs' only lists jobs but does not wait.

The 'wait' command can take a process ID to wait for that specific job.

3fill in blank

hard

Fix the error in the code to properly wait for all background jobs before printing "Finished".

Bash Scripting

sleep 4 & sleep 3 & sleep 2 & [1]; echo "Finished"

Drag options to blanks, or click blank then click option'

Await $!

Bwait

Csleep

Dkill

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'wait $!' waits only for the last job, not all jobs.

Using 'sleep' or 'kill' does not wait properly.

Using 'wait' without arguments waits for all background jobs, ensuring 'Finished' prints last.

4fill in blank

hard

Fill both blanks to create a loop that waits for each background job individually using their PIDs stored in an array.

Bash Scripting

pids=(); sleep 3 & pids+=($!); sleep 2 & pids+=($!); for pid in "${pids[@]}"; do [1] $pid; done; echo [2]

Drag options to blanks, or click blank then click option'

Await

Bsleep

C"All jobs done"

D"Done"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sleep' inside the loop does not wait for jobs.

Printing the wrong message or before waiting.

The loop uses 'wait' on each PID to wait for each job, then prints a message after all finish.

5fill in blank

hard

Fill all three blanks to start three background jobs, wait for all, and then print a summary message.

Bash Scripting

sleep 1 & sleep 2 & sleep 3 & [1]; echo [2] [3]

Drag options to blanks, or click blank then click option'

Await

B"All"

C"background jobs finished"

Dsleep

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sleep' instead of 'wait' does not wait for jobs.

Printing message before waiting.

The 'wait' command pauses until all jobs finish, then the echo prints a clear message.

Practice

1. What does the wait command do in a bash script when used without any arguments?

easy

A. It pauses the script until all background processes finish.

B. It immediately terminates all background processes.

C. It lists all running background processes.

D. It restarts the last background process.

Solution

1. Step 1: Understand the role of wait without arguments

   The wait command without arguments pauses the script until all background jobs started by the script finish.

2. Step 2: Compare with other options

   It does not terminate, list, or restart processes; it only waits for their completion.

3. Final Answer:

   It pauses the script until all background processes finish. -> Option A

4. Quick Check:

   wait without args = pause for all background jobs [OK]

Hint: No args means wait for all background jobs to finish [OK]

Common Mistakes:

• Thinking wait kills processes
• Assuming wait lists processes
• Confusing wait with restart commands

2. Which of the following is the correct syntax to wait for a specific background process with PID stored in variable pid?

easy

A. wait pid

B. wait $pid

C. wait --pid $pid

D. wait -p $pid

Solution

1. Step 1: Recall the syntax for waiting on a specific PID

   The correct syntax is wait $pid, where $pid is the process ID variable.

2. Step 2: Identify incorrect options

   Options with flags like -p or --pid are invalid in bash. Also, wait pid without $ won't expand the variable.

3. Final Answer:

   wait $pid -> Option B

4. Quick Check:

   Use wait with $pid to wait for that process [OK]

Hint: Use wait followed by $pid to wait for one process [OK]

Common Mistakes:

• Using flags like -p or --pid which don't exist
• Forgetting the $ to expand variable
• Passing variable name without $

3. Consider this script snippet:

sleep 3 & pid1=$!
sleep 5 & pid2=$!
wait $pid1
echo "First done"
wait $pid2
echo "Second done"

What will be the order of printed lines?

medium

A. First done\nSecond done

B. Second done\nFirst done

C. First done\nFirst done

D. Second done\nSecond done

Solution

1. Step 1: Understand background jobs and wait order

   Two sleep commands run in background: one sleeps 3 seconds, the other 5 seconds. wait $pid1 waits for the 3-second sleep to finish first.

2. Step 2: Trace the echo outputs

   After the first wait, it prints "First done". Then it waits for the 5-second sleep and prints "Second done".

3. Final Answer:

   First done Second done -> Option A

4. Quick Check:

   Waits print in order of completion [OK]

Hint: Wait commands print in order of waited process completion [OK]

Common Mistakes:

• Assuming both echo print immediately
• Confusing order of wait calls
• Ignoring background process durations

4. What is wrong with this script snippet?

sleep 4 &
wait pid
echo "Done"

Assuming pid is not defined.

medium

A. The script will wait for all background jobs anyway.

B. The script will wait for a process named 'pid'.

C. The script will throw an error because pid is undefined.

D. The script will ignore the wait command.

Solution

1. Step 1: Check variable usage in wait command

   The script uses wait pid without a $ sign, so bash treats 'pid' as a literal string, not a variable.

2. Step 2: Understand effect of undefined variable

   Since 'pid' is not a valid PID and not defined, wait will fail with an error about invalid PID or job.

3. Final Answer:

   The script will throw an error because pid is undefined. -> Option C

4. Quick Check:

   Use $pid to expand variable; missing $ causes error [OK]

Hint: Always use $ before variable names in wait [OK]

Common Mistakes:

• Forgetting $ before variable
• Assuming wait accepts names
• Ignoring error messages

5. You want to run three commands in background, capture their PIDs, and then wait specifically for those three processes to finish before continuing. Which script snippet correctly does this?

hard

A. cmd1 & pid1=$!; cmd2 & pid2=$!; cmd3 & pid3=$!; wait

B. cmd1 & cmd2 & cmd3 & wait $!

C. cmd1 & cmd2 & cmd3 & wait

D. cmd1 & pid1=$!; cmd2 & pid2=$!; cmd3 & pid3=$!; wait $pid1 $pid2 $pid3

Solution

1. Step 1: Understand background process tracking

   Each command runs in background and its PID is saved in separate variables.

2. Step 2: Use wait with all PIDs

   Using wait $pid1 $pid2 $pid3 waits for all three specific processes to finish.

3. Step 3: Analyze other options

   cmd1 & cmd2 & cmd3 & wait $! (cmd1 & cmd2 & cmd3 & wait $!) waits only for last background job. cmd1 & cmd2 & cmd3 & wait (cmd1 & cmd2 & cmd3 & wait) waits for all background jobs but does not track PIDs explicitly. cmd1 & pid1=$!; cmd2 & pid2=$!; cmd3 & pid3=$!; wait saves PIDs but then uses wait without arguments, so the PID variables are unused and it waits for all jobs.

4. Final Answer:

   cmd1 & pid1=$!; cmd2 & pid2=$!; cmd3 & pid3=$!; wait $pid1 $pid2 $pid3 -> Option D

5. Quick Check:

   Wait with all PIDs ensures all specific jobs finish [OK]

Hint: Save PIDs and wait for all to ensure completion [OK]

Common Mistakes:

• Waiting only for last PID
• Not saving PIDs before wait
• Assuming wait without args always works as expected