Expand description
Support for sysexits codes
Constants
A (user specified) output file cannot be created.
Something was found in an unconfigured or misconfigured state.
The input data was incorrect in some way. This should only be used for
user’s data and not system files.
An error occurred while doing I/O on some file.
The host specified did not exist. This is used in mail addresses or
network requests.
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).
You did not have sufficient permission to perform the operation. This
is not intended for file system problems, which should use
NoInput or
CantCreat, but rather for high level permissions.The user specified did not exist. This might be used for mail addresses
or remote logins.
The process exited successfully.
An operating system error has been detected. This is intended to be
used for such things as “cannot fork”, or “cannot create pipe”. It
includes things like getuid(2) returning a user that does not exist
in the passwd file.
Some system file (e.g. /etc/passwd, /var/run/utmp) does not exist,
cannot be opened, or has some sort of error (e.g. syntax error).
The remote system returned something that was “not possible” during a
protocol exchange.
A service is unavailable. This can occur if a support program or file
does not exist. This can also be used as a catch-all message when
something you wanted to do doesn’t work, but you don’t know why.
An internal software error has been detected. This should be limited
to non-operating system related errors if possible.
Temporary failure, indicating something that is not really an error.
For example that a mailer could not create a connection, and the
request should be reattempted later.
The command was used incorrectly, e.g. with the wrong number of
arguments, a bad flag, bad syntax in a parameter, or whatever.
Traits
Extension for converting errors to
ExitFunctions
Convert
std::io::ErrorKind to a Code