How to Make a Bash Script Wait for a Command to Finish

by

In the world of automation and scripting, the ability to manage background processes is crucial for effective task execution. This tutorial will guide you through the process of creating a Bash script that starts a background task and efficiently waits for it to finish before proceeding with further commands. By leveraging the process ID (PID) of the background job and the wait command, you can ensure controlled execution flow and resource management.

Prerequisites

  • Basic knowledge of Bash scripting.
  • Understanding of variables and processes.
  • Familiarity with the sleep command and background execution using &.
  • No additional packages are required for this basic script.

DID YOU KNOW?

Using background processes can significantly improve the performance of your scripts by allowing them to perform multiple tasks concurrently without blocking the main execution thread.

The Script

Below is a simple Bash script that demonstrates how to initiate a background process, captures its PID, and waits for its completion before executing further commands. In this example, we simulate a long-running task using the sleep command.

#!/bin/bash

# Start a background process
date # Print current time
sleep 5 &

# Capture the Process ID
PID=$!

# Wait for the background process to finish
echo "Waiting for the background process with $PID ID to finish..."
wait $PID

# Continue with the script
date # Print current time after command completion
echo "Background process has finished."

Step-by-Step Explanation

NOTE!

If you use wait without specifying a PID, it will wait for all background processes to complete. Specifying the exact PID ensures you only wait for the intended process.

Let’s break down the script into manageable steps:

  1. Start a Background Process: The script initiates a background process using sleep 5 &, allowing the script to continue running while waiting for this task.
  2. Capture the Process ID: Immediately after starting the background task, we store its process ID using PID=$!. This is critical for later control.
  3. Wait for the Background Process: The wait $PID command pauses the script’s execution until the background job identified by PID completes.
  4. Continue Execution: Once the background task finishes, the script resumes and executes the echo statement, confirming completion.
How to Make a Bash Script Wait for a Command to Finish
How to Make a Bash Script Wait for a Command to Finish

How to Run the Script

To execute the script, follow these steps:

  1. Create a new file called script.sh using a text editor.
  2. Copy the Bash script content into this file and save it.
  3. Run the script by executing bash script.sh in your terminal.

Conclusion

By using background processes and the wait command, you can effectively manage your scripts, allowing for both concurrent processing and controlled execution flow. This method is particularly useful when dealing with tasks that might take a considerable amount of time to complete. Experiment with different commands and processes to see how you can enhance your Bash scripts further!

FAQ

  1. What does the wait command do?

    The wait command waits for all background processes to complete, or it can wait for a specific process ID if provided.

  2. Can I run multiple background processes at the same time?

    Yes, you can start multiple background processes and capture their PIDs similarly to manage them individually.

  3. What happens if I don’t use wait?

    If you skip the wait command, your script will not pause for the background process to finish, which can lead to unexpected behavior or premature execution of subsequent commands.

  4. Can I use other commands instead of sleep?

    Yes, you can replace sleep with any long-running command, such as data processing or downloading files.

Troubleshooting

Here are some common issues you might encounter while executing your Bash script and their solutions:

  • Permission Denied: If you see this error, make sure the script is executable by running chmod +x script.sh.
  • Command Not Found: Ensure that all commands used in the script are installed and available on your PATH.
  • Unexpected Output: Check if the background process is correctly launched and that you capture the correct PID.
  • Script Exits Prematurely: Ensure that the wait command is correctly placed after the process initiation.

 

 

© 2025 BashScript.net