Re: RFC: error codes on exit
- From
Bagas Sanjaya <bagasdotme@gmail.com>
- Date
- May 22, 2021, 04:06 UTC
- Message-ID
- <657d3d24-2f08-f076-5c84-9ae434149530@gmail.com>
- In-Reply-To
- <dc14c50d-c626-19f8-e615-52ca3c9051dc@zytor.com>
On 22/05/21 06.20, H. Peter Anvin wrote:
Show 5 quoted lines
> > <sysexits.h> > > -hpa >
Looking that header file you mention, I saw:
Show 19 quoted lines
> #define EX_OK 0 /* successful termination */ > > #define EX__BASE 64 /* base value for error messages */ > > #define EX_USAGE 64 /* command line usage error */ > #define EX_DATAERR 65 /* data format error */ > #define EX_NOINPUT 66 /* cannot open input */ > #define EX_NOUSER 67 /* addressee unknown */ > #define EX_NOHOST 68 /* host name unknown */ > #define EX_UNAVAILABLE 69 /* service unavailable */ > #define EX_SOFTWARE 70 /* internal software error */ > #define EX_OSERR 71 /* system error (e.g., can't fork) */ > #define EX_OSFILE 72 /* critical OS file missing */ > #define EX_CANTCREAT 73 /* can't create (user) output file */ > #define EX_IOERR 74 /* input/output error */ > #define EX_TEMPFAIL 75 /* temp failure; user is invited to retry */ > #define EX_PROTOCOL 76 /* remote error in protocol */ > #define EX_NOPERM 77 /* permission denied */ > #define EX_CONFIG 78 /* configuration error */
For EX_USAGE case, we may sometimes display correct usage syntax so that users can fix their typing.
We may use EX_CONFIG when we encounter any errors when parsing .gitconfig.
EX_OSFILE isn't necessary for Git, though.
-- An old man doll... just what I always wanted! - Clara