a technical notebook

scratch 1.1KB

1234567891011121314151617181920212223
  1. Doing a little Bash scripting:
  2. [Reading on exit codes](http://www.rdio.com/artist/Carolina_Chocolate_Drops/album/Dona_Got_a_Ramblin%27_mind/).
  3. [And](http://www.tldp.org/LDP/abs/html/exitcodes.html#EXITCODESREF):
  4. > There has been an attempt to systematize exit status numbers (see
  5. > /usr/include/sysexits.h), but this is intended for C and C++ programmers. A
  6. > similar standard for scripting might be appropriate. The author of this
  7. > document proposes restricting user-defined exit codes to the range 64 - 113
  8. > (in addition to 0, for success), to conform with the C/C++ standard. This
  9. > would allot 50 valid codes, and make troubleshooting scripts more
  10. > straightforward. [2] All user-defined exit codes in the accompanying examples
  11. > to this document conform to this standard, except where overriding
  12. > circumstances exist, as in Example 9-2.
  13. For the moment, a reasonable pattern to follow seems like:
  14. 1. If it's just some general error, `exit 1`
  15. 2. If I want to specify meaningful codes, use something 64-113.
  16. * [Debian New Maintainers' Guide](https://www.debian.org/doc/manuals/maint-guide/)