Terminating Processes: kill, killall, pkill & Signals
Processes communicate and terminate via POSIX signals. The `kill` command sends signals to PIDs, `pkill` matches process names with regex, and `killall` terminates all instances of a binary. Always start with graceful `SIGTERM` (15) before resorting to uncatchable `SIGKILL` (9).
"SIGTERM (15) is like knocking on a worker's door and saying "Please pack your belongings and clock out"; SIGKILL (9) is like cutting the building power with a chainsaw."
Deep Dive: How It Works
Key Signals: `SIGTERM (15)` (graceful exit, allows flushing files/closing DBs), `SIGKILL (9)` (immediate kernel kill, cannot be caught or ignored), `SIGHUP (1)` (reload configuration), `SIGINT (2)` (Ctrl+C interrupt).
kill vs pkill: `kill <PID>` requires numeric process IDs; `pkill <name>` matches process names directly.
Graceful Escalation: Send SIGTERM, wait 5 seconds, and send SIGKILL only if process fails to exit.
Syntax Blueprint
kill 12345 # Graceful SIGTERM (15) kill -9 12345 # Forceful SIGKILL (9) pkill -f "node server.js" # Kill by full commandline match killall nginx # Kill all nginx instances
Always attempt graceful termination (SIGTERM) before forcing SIGKILL.
Core Rules to Remember
Common Beginner Traps & How to Fix Them
Using `kill -9` as the default first response for any stuck process.Why it happens: Developers learn that `kill -9` always works.
How to fix: Default to standard `kill <PID>` (SIGTERM); escalate to `-9` only if unresponsive.
Live Interactive Example
Hit Run Code to see it liveYour Turn: Micro Challenge
No pressure! Edit the starter code below and test your solution with instant feedback.
Spawn and Terminate a Sleep Process
- Spawn `sleep 30 &` in the background.
- Terminate it using `kill $!`.
- Wait on it with `wait $! 2>/dev/null` and echo "Terminated".
Finished reading and practicing?
Mark this lesson as completed to update your course progress.