úÎ!<:"      !!BSD exit codes exposed to Haskell(c) Justus Adam, 2015 - 2018BSD-3dev@justus.science experimentalPOSIXSafe9 " exit-codessuccessful termination (0)=The successful exit is always indicated by a status of 0, or . exit-codessuccessful termination (0) exit-codes"base value for error messages (64)Error numbers begin at j to reduce the possibility of clashing with other exit statuses that random programs may already return. exit-codescommand line usage error (64)‚The command was used incorrectly, e.g., with the wrong number of arguments, a bad flag, a bad syntax in a parameter, or whatever. exit-codescommand line usage error (64) exit-codesdata format error (65)iThe input data was incorrect in some way. This should only be used for user's data and not system files. exit-codesdata format error (65) exit-codescannot open input (66)žAn input file (not a system file) did not exist or was not readable. This could also include errors like "No message" to a mailer (if it cared to catch it). exit-codescannot open input (66)  exit-codesaddressee unknown (67)ZThe user specified did not exist. This might be used for mail addresses or remote logins.  exit-codesaddressee unknown (67)  exit-codeshost name unknown (68)VThe host specified did not exist. This is used in mail addresses or network requests.  exit-codeshost name unknown (68)  exit-codesservice unavailable (69)ÉA service is unavailable. This can occur if a support program or file does not exist. This can also be used as a catchall message when something you wanted to do doesn't work, but you don't know why. exit-codesservice unavailable (69) exit-codesinternal software error (70)yAn internal software error has been detected. This should be limited to non-operating system related errors as possible. exit-codesinternal software error (70) exit-codessystem error (71)çAn operating system error has been detected. This is intended to be used for such things as "cannot fork", "cannot create pipe", or the like. It includes things like getuid returning a user that does not exist in the passwd file. exit-codessystem error (71) exit-codescritical OS file missing (72)Some system file (e.g., etcpasswd, varrun/utmpZ, etc.) does not exist, cannot be opened, or has some sort of error (e.g., syntax error). exit-codescritical OS file missing (72) exit-codes%can't create (user) output file (73)1A (user specified) output file cannot be created. exit-codes%can't create (user) output file (73) exit-codesinput/output error (74)/An error occurred while doing I/O on some file. exit-codesinput/output error (74) exit-codes+temp failure; user is invited to retry (75)¿Temporary failure, indicating something that is not really an error. In sendmail, this means that a mailer (e.g.) could not create a connection, and the request should be reattempted later. exit-codes+temp failure; user is invited to retry (75) exit-codesremote error in protocol (76)XThe remote system returned something that was "not possible" during a protocol exchange. exit-codesremote error in protocol (76) exit-codespermission denied (77)‚You did not have sufficient permission to perform the operation. This is not intended for file system problems, which should use  or *, but rather for higher level permissions. exit-codespermission denied (77) exit-codesconfiguration error (78)>Something was found in an unconfigured or misconfigured state.  exit-codesconfiguration error (78)! exit-codesmaximum listed value (78)"  !"  !"      !"#$'exit-codes-1.0.0-2tqixLmLu2jIugukc77v9ySystem.Exit.CodesexOkcodeOkexBaseexUsage codeUsage exDataErr codeDataErr exNoInput codeNoInputexNoUser codeNoUserexNoHost codeNoHost exUnavailablecodeUnavaiable exSoftware codeSoftwareexOsErr codeOsErrexOsFile codeOsFile exCantCreatecodeCantCreateexIOErr codeIOErr exTempFail codeTempFail exProtocol codeProtocolexNoPerm codeNoPermexConfig codeConfigexMax