4 ms·

Some programs do follow a specification (sysexits.h) where numbers 64 and higher are used for common uses, such as usage error, software error, file format erro

• ithkuil 5y ago
  Aldo when the oomkiller process kills another process it causes it to exit with a well known exit code: 137
  • saagarjha 5y ago
    That’s just 128+SIGKILL (9).
  • teddyh 5y ago
    That’s not an exit code; that is a fake exit code which your shell made up, since your shell has no other way to tell you that a process did not exit at all, but was killed by a signal (9, i.e. SIGKILL). This is, again, not an actual exit code, since the process did not actually exit. See here for why you can’t use an exit status of 128+signal to fake a “killed by signal” state, either: https://www.cons.org/cracauer/sigint.html https://www.cons.org/cracauer/sigint.html