Shell Scripting / Bash Tricks

Stop your bash scripts from dying in silence when a command fails

🧩 The Challenge

You write a 50-line script, run it, and it silently skips the mission-critical backup step because a simple mkdir failed midway through. It’s infuriating when you think you have a clean archive, but you actually just have a mess of broken files.

💡 The Fix

Flip the switch that forces bash to exit immediately if any command returns a non-zero status code. It turns your scripts from dangerous loose cannons into programs that actually respect error boundaries.

set -euo pipefail

⚙️ Why It Works

Adding this to the top of your scripts ensures that errors in pipes don’t get ignored, undefined variables trigger an immediate halt, and failed commands stop the execution flow before the damage gets worse.

🚀 Pro-Tip: Always include this in your shebang lines; it’s the single best way to catch bugs before they hit production.

Linux Tips & Tricks | © ngelinux.com | 7/28/2026