Expand description
Common exit codes for applications.
§Example
extern crate exit_code;
::std::process::exit(exit_code::SUCCESS);
Constants§
- CANNOT_
CREATE - A (user specified) output file cannot be created.
- CONFIG_
ERROR - Something was found in an unconfigured or misconfigured state.
- DATA_
ERROR - The input data was incorrect in some way. This should only be used for user’s data and not system file.
- FAILURE
- Unsuccessful termination. This is a catch-all error code that should only be used by processes if the reason for the failure is unknown.
- IO_
ERROR - An error occurred while doing I/O on some file.
- NO_HOST
- The host specified did not exist. This is used in mail addresses of network requests.
- NO_
INPUT - 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).
- NO_
PERMISSION - Insufficient permissions to perform an operation. This is not intended for
file system problems, which should use
NO_INPUT
orCANNOT_CREATE
, but rather for higher level permissions. - NO_USER
- The user specified did not exist. This might be used for mail addresses or remote logins.
- OS_
ERROR - 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 thepasswd
file. - OS_
FILE_ ERROR - Some system file (e.g.,
/etc/passwd
,/var/run/utmp
, etc.) does not exist, cannot be opened, or has some sort of error (e.g., syntax error). - PROTOCOL_
ERROR - The remote system returned something that was “not possible” during a protocol exchanged.
- SERVICE_
UNAVAILABLE - 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.
- SOFTWARE_
ERROR - An internal software error has been detected. This should be limited to non-operating system related errors.
- SUCCESS
- Successful termination.
- TEMPORARY_
FAILURE - 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. - USAGE_
ERROR - The command was used incorrectly, e.g., with the wrong number of arguments, a bad flag, a bad syntax in a parameter, or whatever.
Functions§
- is_
reserved - Check if the given exit code is reserved and has a special meaning in a shells.
- is_
valid - Check if the given exit code is in [0..256].