Why Exit codes ($?) in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if your script could instantly know when something goes wrong and fix it on the spot?

The Scenario

Imagine you run a series of commands in your terminal one by one, but you have no way to know if each command worked or failed unless you carefully watch every message. If you miss an error message, you might continue with wrong assumptions.

The Problem

Manually checking if each command succeeded is slow and easy to forget. You might waste time fixing problems later or cause bigger issues because you didn't catch errors early. It's like driving blindfolded hoping the road is clear.

The Solution

Exit codes give you a simple number after each command that tells if it worked (usually 0) or failed (non-zero). You can use this number to automatically decide what to do next, making your scripts smart and reliable.

Before vs After

✗ Before

command
# No check if command worked
next_command

✓ After

command
if [ $? -eq 0 ]; then
  next_command
fi

What It Enables

Exit codes let your scripts catch errors early and react automatically, saving time and avoiding mistakes.

Real Life Example

When installing software, exit codes help the script know if the install succeeded before trying to start the program, preventing crashes.

Key Takeaways

Exit codes tell if a command succeeded or failed.

They help automate decision-making in scripts.

Using them makes your scripts safer and smarter.