Hacker News new | ask | show | jobs
by gruseom 5647 days ago
Looking for more about this, I found a pretty good post:

http://www.davidpashley.com/articles/writing-robust-shell-sc...

1 comments

Just be aware that using 'set -e', while good advice in general, won't catch everything. Particularly lists and sub-shells may return with the status code of the last command, not the failed command, depending on how they were used. So it is possible a command failed within but won't trigger the -e.

The best way is to write the compound commands and any sub-shell commands so that they will exit with the return status of any command that failed, using, say, &&.