Common exit codes for applications.
extern crate exit_code; ::std::process::exit(exit_code::SUCCESS);
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 file.
Unsuccessful termination. This is a catch-all error code that should only be used by processes if the reason for the failure is unknown.
An error occurred while doing I/O on some file.
The host specified did not exist. This is used in mail addresses of 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).
Insufficient permissions to perform an operation. This is not intended for
file system problems, which should use
The user specified did not exist. This might be used for mail addresses or remote logins.
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
Some system file (e.g.,
The remote system returned something that was “not possible” during a protocol exchanged.
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.
An internal software error has been detected. This should be limited to non-operating system related errors.
Temporary failure, indicating something that is not really an error. In
The command was used incorrectly, e.g., with the wrong number of arguments, a bad flag, a bad syntax in a parameter, or whatever.
Check if the given exit code is reserved and has a special meaning in a shells.
Check if the given exit code is in [0..256].