Shell Scripting / Bash Tricks

Stop your scripts from silently failing inside pipes

🧩 The Challenge

You know that feeling when you pipe a command into grep and it looks like it worked, even though the first part crashed and burned? I’ve spent way too many nights debugging empty logs because the script just kept right on chugging.

💡 The Fix

Flip a single internal bash setting that forces the entire pipeline to report the exit status of the very last command that actually failed. It’s a lifesaver for making sure your automated jobs don’t lie to you.

set -o pipefail

⚙️ Why It Works

Bash defaults to only caring about the exit code of the final command in a pipe, but this flag changes that behavior so it returns a non-zero exit status if any component of the pipe hits a wall.

🚀 Pro-Tip: Put this at the top of every script you write; consider it your early warning system.

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