@
@
@ntkt2011-08-02 01:49:13
*nix-like systems
@ntkt, 2011-08-02 01:49:13

Comparative table of errno codes and decodings for various Unixes?

Ladies and gentlemen, I recently lost one very handy thing :(
Namely, a table that brought together common system error codes with decryptions (from errno.h) for the most common *nix-compatible axes - Linux, BSD, AIX, Solaris, HP-UX at least
... Attempts to google it did not lead to anything, which makes you think about your own sanity, professional suitability, etc.
The value of such a table is that the POSIX standard specifies only symbolic names-abbreviations of errors (ENOMEM, such as ), and not codes that differ from axis to axis. And the mass of software that is legible in friends gives in the logs not a decryption and not even a character code, but a stupidly numeric code ...
Parsing at an isolated station a gigabyte pack of incident logs from a highly heterogeneous bundle of software on different axes, without such a table in front of your eyes, you have to make a lot of unnecessary movements. Like, I saw 79 - but while you're reading the log, sit back and remember that on AIX it's Connection Refused, when it's 146 on solarium and Linux, and 239 on xpux.
Naturally, you can always find errno.h on the network from each of the necessary axes, parse, bring together, check with examples and edit, but this is not an hour's work, and this wonderful tablet was already with the author's comments, formatted, etc., and even fit on A4, it seems.
For TCP/IP errors , there is a similar table from IBM from the DB2 mana, which...
In terms of popularity, the "same" table should be likeRosetta Stone for Unix , therefore I ask for your help.
Suddenly, someone has a miracle tablet lying around?
Well, if you don’t find it, leave your wishes anyway, then I’ll do the compilation myself.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
L
lesha_penguin, 2011-08-02
@lesha_penguin

If in order to write to the logs, you can use more or less standard tools:
1) Global table const char* sys_errlist[];
2) the Posix-recommended strerror() function;
3) And finally, you can “quickly and easily” swear in stderr using perror ()
It is clear that I told you the portable / compatible solution methods.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question