> I once deleted a /lib directory due to a misspelled variable in a script! Ah yes, the old "rm -rf $TEMPBASEEDIR/lib" bug. It is so easy to have that happen.

> I once deleted a /lib directory due to a misspelled variable in a script! Ah yes, the old "rm -rf $TEMPBASEEDIR/lib" bug. It is so easy to have that happen. Or like I did, write a script that assumes a certain environment variable is set outside the script... and then forget to set the variable before running it! To prevent these problems, use "set -u" at the top of your bash scripts. This will halt the script instead of silently inserting an empty string if you use an undefined variable. "set -e" (halt on nonzero return code) and "set -o pipefail" (propagate error returns through a pipe) are also useful options, or combine them with: set -euo pipefail Here's a great article that describes these options and some tips for using them: http://redsymbol.net/articles/unofficial-bash-strict-mode/ http://redsymbol.net/articles/unofficial-bash-strict-mode/