As soon as you need to handle errors programmatically I heartily
suggest that you switch to a language with fewer quirks than sh.
Basically that. `set -e` is evil. As soon as you need to handle errors programmatically I heartily
suggest that you switch to a language with fewer quirks than sh.
Basically that. `set -e` is evil.E.g. grep considers no matches worthy of a non-zero (a.k.a. error) exit code while df considers an invalid block size an error worthy of a exit code of zero. Ostensibly printf(1) exits with non-zero on an error, but a format specifier with insufficient arguments is not an error.
set -euo pipefail should be the default so that the script exits on at least some unexpected state/command results. If you want to do more then that with various fallbacks etc... then use another language.
https://stackoverflow.com/questions/4072984/how-do-i-get-the...
https://serverfault.com/questions/143445/what-does-set-e-do-...
pipefail is worse because tools like grep return non-zero for things that aren't inherently errors. Error handling in sh-like shells is archaic enough that if you're reaching for it you should strongly consider reaching for a different language.
I'm saying that a script which would have the potential to fail unintuitively from `set -eup pipefail` probably shouldn't be written in shell and most definitely shouldn't continue to execute once an unexpected state has occured.
You're right that there are a lot of cases in which non-zero exitcodes are the expected behaviour. But if you're accepting these commands with non-zero exitcodes then you're already doing error handling by verifying the output of the commands (at least hopefully), which was the original criteria from the OP for writing the script in another language.