Bash Decision Scripts Made Simple (Part 13 / 34)

While writing a Bash script with a simple sequential list of commands has some utility, this type of scripting is very limiting. A script truly comes into its own when it can make decisions automatically based on conditions or command results. Bash conditional statements allow scripts to react differently depending on the situation, such as checking free disk space, verifying user accounts, testing file existence, or validating command execution. In this guide, we walk through 11 practical decision-making scripts based on real system administration tasks, all tested on Ubuntu 24.04 and Rocky Linux 9.

If you are brand new to shell scripting, start with the basics of Bash scripting first, then come back here to level up your scripts with real decision logic.

The bash if statement checks a condition and runs a block of commands only when that condition is true. The structure looks simple but there are a few rules that trip up beginners every time.

Here is the most basic form. The script checks whether a number is greater than 100:

The fi at the end closes the block. Every if needs a matching fi or the script will not even run. Read more about the complete bash if statement guide for more syntax variations.

Most real decisions are not binary. A service can be running, stopped, or not installed at all. The bash if elif else chain handles all three states cleanly. Here is a practical script that checks a system user's existence, something you might run during server provisioning on Ubuntu or Rocky Linux.

For more on handling user input inside scripts, see the guide on bash read command with user input examples.

This is the biggest gap in most tutorials. Single brackets [ ] are POSIX-compliant and work in any shell. Double brackets [[ ]] are a Bash-specific extension and are generally safer and more powerful. Almost no article written before 2024 covers this properly.

File tests are one of the most used parts of shell script decision making in real sysadmin work. Before writing to a file, touching a directory, or running a backup, your script should always check what it is dealing with. Here is every file test operator you need:

The following two operators test string length, not file properties. They are commonly used alongside file tests inside the same scripts:

Here is a real script that validates a log file before processing it:

This pattern — check, then act — is used in virtually every production backup and automation script. Learn more about the bash exit codes and error handling to combine file tests with proper error reporting.

Every Linux command returns an exit code. Zero means success. Anything else means something went wrong. This is one of the most practical forms of bash conditional statements in real sysadmin scripts, and almost no beginner article covers it.

Here is a real-world service status check script that works on both Ubuntu and Rocky Linux:

This kind of script is what you would run from a cron job every few minutes to keep critical services alive automatically.

You do not always need a full if block. The && and || operators let you write conditional logic in a single line. They are widely used in real shell scripts but rarely explained in beginner articles.

• command1 && command2 — run command2 only if command1 succeeds (exit 0)
• command1 || command2 — run command2 only if command1 fails (non-zero exit)

Here are three production-grade decision scripts used by Linux sysadmins daily. These replace the toy examples with actual automation that solves real problems.

Script 1 — Disk Usage Alert (works on Ubuntu and Rocky Linux)

For more disk monitoring examples, see the df command guide with examples and du command usage.

Script 2 — Automatic Linux Server Backup with Conditional Checks

See the full automatic Linux backup script guide for a more complete version with rotation and email alerts.

When you have five or more conditions to check on the same variable, a chain of elif blocks gets messy fast. The case statement is cleaner and easier to read. Think of it as a switch statement for Bash.

The *) wildcard at the end acts as the default catch-all. Always include it in production scripts so unexpected input is handled gracefully. See the full bash case statement guide for more pattern matching examples.

Sometimes one condition is not enough. You need to check two things at once. There are two ways to combine conditions in Bash, and it matters which one you use.

When your if statement is not behaving the way you expect, the fastest fix is to run the script with bash -x. This prints every command before it runs, so you can see exactly what value was in each variable when the condition was evaluated.

The + prefix on each line is the trace output. You can see the actual value that was tested. This saves a lot of time compared to adding echo statements everywhere. See the Linux shell scripting cheat sheet for a quick reference of other useful debug flags.

These are the actual error messages that break Bash if-else scripts, and what causes them. This section exists because no other tutorial covers it, and it is exactly where beginners get stuck.

Mastering bash conditional statements is the step that takes your scripts from simple command lists to real automation tools. This guide covered 11 practical decision scripts spanning basic if-else blocks, the important [[ ]] vs [ ] distinction, file test operators, exit code conditionals, short-circuit one-liners, case statements, combined conditions, debug techniques, and the five most common errors that trip people up. Each example is tested on Ubuntu 24.04 and Rocky Linux 9 and reflects how scripts are actually written in 2025 production environments.

Keep building on these patterns with the Linux bash scripting automation guide.

Related Articles

• What is Bash Scripting in Linux (Part 1 of 34)
• Bash if Statement Complete Guide with Examples (Part 11 / 34)
• Bash if elif else Statement with Examples (Part 10 of 34)
• Bash Case Statement with Examples (Part 12 / 34))
• Bash Script Exit Codes and Error Handling (Part 5 of 34)
• Linux Shell Scripting Command Cheat Sheet
• Linux Shell Scripting Interview Questions
• Man Bash Page