Process Management in Shell Scripts

# CHAPTER 12

Process Management in Shell Scripts #

1. Introduction #

2. Learning Objectives #

• Identify and monitor active system processes using the ps and top commands.

• Send a script or command to execute silently in the background using &.

• Retrieve the unique Process ID (PID) of background tasks using $!.

• Terminate hanging or rogue processes safely using the kill command.

• Understand the distinction between graceful termination (kill -15) and forceful termination (kill -9).

3. Monitoring Processes (ps) #

# View processes running in your current terminal
ps

# The Holy Grail: View EVERY process running on the entire server
# a = all users, u = show user/memory details, x = show background processes
ps aux

If you are looking for a specific running script, you pipe the massive ps aux output directly into grep: ps aux | grep "backup.sh"

4. Background Execution (& and nohup) #

#!/bin/sh
echo "Initiating massive download..."
# The & sends the wget download to the background
wget http://example.com/massive_file.iso &

echo "Download is running in the background. I am free to do other work!"

*The Disconnect Problem:* If you start a background task and then log out of your SSH session, the task will die. To prevent this, use nohup (No Hangup).

nohup ./long_script.sh &

5. Tracking the PID ($!) #

#!/bin/sh
echo "Starting background backup..."
./slow_backup.sh &

# Capture the PID
BACKUP_PID=$!
echo "Backup is running under PID: $BACKUP_PID"

6. Terminating Processes (kill) #

There are two primary ways to kill:

1. 1. Graceful (kill -15 or SIGTERM): This asks the program nicely to shut down. The program is allowed to save its files and close its connections before dying. (This is the default if you just type kill 1234).

1. 2. Forceful (kill -9 or SIGKILL): This is the nuclear option. The kernel instantly executes the program without warning. Data corruption may occur.

# Gracefully ask PID 5432 to stop
kill 5432

# Forcefully annihilate PID 5432
kill -9 5432

7. Diagrams/Visual Suggestions #

8. Best Practices #

• Always try kill before kill -9: In a script, if you need to restart a service, you should attempt a graceful kill first, followed by a short sleep 2 to give it time to die, before escalating to the destructive kill -9 command. This preserves database integrity and prevents corrupt cache files.

9. Common Mistakes #

• Killing the grep process: If you type ps aux | grep my_script, the terminal often returns *two* lines. One is your script, and the other is the grep command itself (because grep is currently running to search for the word!). Beginners often accidentally grab the PID of the grep process and try to kill it, resulting in a confusing "No such process" error.

10. Mini Project: The Timeout Sentinel #

1. 1. nano sentinel.sh

1. 2. Write the code:

#!/bin/sh

echo "Starting risky network task..."

# 1. Start a task that will intentionally hang (sleep 10) in the background
sleep 10 &
TASK_PID=$!

echo "Task running with PID: $TASK_PID"
echo "Waiting 5 seconds for completion..."
sleep 5

# 2. Check if the task is still running
# 'kill -0' doesn't actually kill. It just checks if the PID exists!
if kill -0 $TASK_PID 2>/dev/null; then
    echo "TIMEOUT REACHED! Task is hanging. Executing SIGKILL..."
    kill -9 $TASK_PID
    echo "Task terminated."
else
    echo "Task finished successfully on its own."
fi

1. 3. Run it. You have engineered an active timeout monitor that prevents rogue processes from permanently freezing your system!

11. Practice Exercises #

1. 1. Explain the operational difference between executing a script using the command ./script.sh versus nohup ./script.sh &.

1. 2. Detail the critical distinction between the kill -15 signal and the kill -9 signal. Why is -9 considered the absolute last resort?

12. MCQs with Answers #

13. Interview Questions #

• Q: A developer complains that their automated reporting script successfully starts a background task, but the background task instantly dies the moment their SSH session disconnects from the server. Explain the mechanism causing this termination, and provide the exact command syntax required to immunize the background task against session disconnection.

• Q: Walk me through the exact terminal workflow you would execute if you discovered a script was trapped in an infinite while loop, consuming 100% of a CPU core, and completely ignoring standard Ctrl+C termination attempts.

• Q: Explain the purpose of the kill -0 command when utilized inside a shell script. Why is it an essential tool for monitoring the lifespan of background jobs?

14. FAQs #

15. Summary #

16. Next Chapter Recommendation #