Bash strict mode is a useful scripting practice that helps you write safer and more reliable Bash scripts. By default, Bash scripts may continue running even when a command fails, a variable is missing, or a command inside a pipeline returns an error. This can create serious problems in automation scripts, backup scripts, deployment scripts, and cybersecurity scripts.
Strict mode helps detect these problems early. It is commonly written as:
set -euo pipefail
If you are learning Bash scripting, understanding strict mode will help you avoid hidden errors and write cleaner scripts.
Bash strict mode is not a separate feature or command. It is a combination of Bash options that change how a script behaves when errors happen.
The common strict mode line is:
set -euo pipefail
This line is usually added near the top of a Bash script, after the shebang.
Example:
#!/bin/bashset -euo pipefailecho "Script started"
The set -e option tells Bash to stop the script when a command fails.
Example:
#!/bin/bashset -eecho "Before error"ls /wrong-directoryecho "This line will not run"
If /wrong-directory does not exist, the script stops immediately. This prevents the script from continuing with bad or missing data.
The set -u option tells Bash to stop the script when an undefined variable is used.
Example:
#!/bin/bashset -uecho "Username is $username"
If the variable username is not defined, Bash stops the script and shows an error. This is useful because spelling mistakes in variable names can otherwise go unnoticed.
Correct example:
#!/bin/bashset -uusername="kali"echo "Username is $username"
By default, Bash checks only the exit status of the last command in a pipeline. The pipefail option makes the pipeline fail if any command inside it fails.
Example:
#!/bin/bashset -o pipefailcat missing-file.txt | grep "error"
If cat fails because the file does not exist, the pipeline is treated as failed.
Create a script:
nano strict-mode.sh
Add this code:
#!/bin/bashset -euo pipefaillog_file="/var/log/auth.log"echo "Checking failed SSH login attempts..."grep "Failed password" "$log_file" | tail -5echo "Check completed"
Run it:
chmod +x strict-mode.sh./strict-mode.sh
This script is safer because it stops if an important error happens.
Bash strict mode helps you write safer scripts by stopping execution when commands fail, undefined variables are used, or pipelines break. The set -euo pipefail line is especially useful for automation, backups, server scripts, and cybersecurity tasks.
For beginners, strict mode is a good habit to learn early. It makes Bash scripts easier to debug and reduces the risk of silent failures.
Introduction Bash scripting is a powerful way to automate Linux tasks, but writing a script…
Introduction A self-signed SSL certificate is a certificate that is created and signed by the…
Introduction Debugging is an important part of Bash scripting. When a script does not work…
Introduction Cron jobs are used in Linux to run commands or Bash scripts automatically at…
Introduction Pipes are an important feature in Linux and Bash scripting. A pipe allows you…
Introduction The grep, awk, and sed commands are powerful text-processing tools in Linux. They are…