Const Something was found in an un-configured or mis-configured 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 EX_NOINPUT or EX_CANTCREAT, but rather for higher level permissions.
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 in-cludes things like getuid returning a user that does not exist in the passwd file.
Some system file (e.g., /etc/passwd, /var/run/utx.active, etc.) 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.
An internal software error has been detected. This should be limited to non-operating system related errors as possible.
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.
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 does not work, but you do not know why.
The command was used incorrectly, e.g., with the wrong number of arguments, a bad flag, a bad syntax in a parameter, or whatever.
Generated using TypeDoc
A (user specified) output file cannot be created.