Why Signal handling with trap in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if your script could clean up after itself every time you stop it suddenly?

The Scenario

Imagine you are running a long script in the terminal, and suddenly you need to stop it safely or clean up temporary files before exiting. Without any special setup, you just press Ctrl+C and hope nothing breaks.

The Problem

Manually stopping scripts can leave your system messy or your data corrupted. You might forget to remove temporary files or close connections, causing errors later. It's slow and risky to handle these interruptions by hand every time.

The Solution

Using trap in bash lets your script catch signals like Ctrl+C and run cleanup code automatically. This means your script can stop safely, remove temporary files, and leave things tidy without you doing anything extra.

Before vs After

✗ Before

echo 'Running...'; sleep 100; echo 'Done'

✓ After

trap 'echo Cleanup; rm -f temp.txt; exit' INT; echo 'Running...'; sleep 100; echo 'Done'

What It Enables

You can make your scripts smart and safe by handling interruptions gracefully, avoiding errors and wasted time.

Real Life Example

When downloading files or processing data, if you press Ctrl+C, the script can delete partial files and close connections properly, so you don't get broken or incomplete results.

Key Takeaways

Manual interruption can cause messy leftovers and errors.

trap lets scripts catch signals and run cleanup code.

This makes scripts safer and more reliable during unexpected stops.