Automatic exit from Bash shell script on error [duplicate]

by

Use the set -e builtin:

#!/bin/bash
set -e
# Any subsequent(*) commands which fail will cause the shell script to exit immediately

Alternatively, you can pass -e on the command line:

bash -e my_script.sh

You can also disable this behavior with set +e.

You may also want to employ all or some of the the -e -u -x and -o pipefail options like so:

set -euxo pipefail

-e exits on error, -u errors on undefined variables, and -o (for option) pipefail exits on command pipe failures. Some gotchas and workarounds are documented well here.

(*) Note:

The shell does not exit if the command that fails is part of the
command list immediately following a while or until keyword,
part of the test following the if or elif reserved words, part
of any command executed in a && or || list except the command
following the final && or ||, any command in a pipeline but
the last, or if the command’s return value is being inverted with
!

(from man bash)

More Related Contents:

  1. Pipe output and capture exit status in Bash
  2. How to check the exit status using an ‘if’ statement
  3. Is there a TRY CATCH command in Bash
  4. Ignoring specific errors in a shell script
  5. What does 2>&1 mean here?
  6. Input data to a shell script [closed]
  7. How to reload .bashrc settings without logging out and back in again?
  8. How do I iterate over a range of numbers defined by variables in Bash?
  9. When do we need curly braces around shell variables?
  10. Bash command line and input limit
  11. Replace one substring for another string in shell script
  12. How to assign the output of a Bash command to a variable? [duplicate]
  13. Multi-dimensional arrays in Bash
  14. How do I check if a directory exists in a Bash shell script?
  15. Checking from shell script if a directory contains files
  16. Escape dollar sign in string by shell script
  17. Open and write data to text file using Bash?
  18. Piping tail output though grep twice
  19. bash set -e and i=0;let i++ do not agree
  20. Why is “[[ 10 < 2 ]]" true when comparing numbers in bash? [duplicate]
  21. How to go to each directory and execute a command?
  22. Relative paths based on file location instead of current working directory [duplicate]
  23. Counting lines or enumerating line numbers so I can loop over them – why is this an anti-pattern?
  24. pipe stdout and stderr to two different processes in shell script?
  25. Why equal to operator does not work if it is not surrounded by space?
  26. In bash, is there an equivalent of die “error msg”
  27. How can I convert tabs to spaces in every file of a directory?
  28. How do I integrate MSYS2 shell into Visual studio code on Window?
  29. Parse HTML using shell
  30. Renaming files with Bash, removing prefix and suffix

Leave a Comment