Prev: Live CD to scan windows pc for a virus
Next: where is CentOS storing my hostname that it resets it on each reboot?
From: Mark Hobley on 4 Apr 2010 15:16
Does anyone know of any repositories containing man pages for system error
messages? I am looking for pages that document error messages and resolution.

Manual pages for each of the error messages produced by the C library would
be a good starting point for me. Has anyone written any such pages?

I am also looking for manual pages for kernel error codes, and any application
specific error messages, or programming environment error messages.

http://markhobley.yi.org/manpages/missingman.html

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/

From: Bit Twister on 4 Apr 2010 16:34
On Sun, 4 Apr 2010 20:16:53 +0100, Mark Hobley wrote:
> Does anyone know of any repositories containing man pages for system error
> messages? I am looking for pages that document error messages and resolution.

That documentation would be pretty impressive. Resolution would depend
on what was going on at the time, where.
Example: Unable to open file.


If you have installed the development package for compiling kernel
source you start by looking through the include files. Example:

$ locate /error.h | grep -v .html | grep -v .hpp
/usr/include/error.h
/usr/include/CLucene/debug/error.h
/usr/include/X11/Xmu/Error.h
/usr/include/alsa/error.h
/usr/include/avahi-common/error.h
/usr/include/bits/error.h
/usr/include/gpgme++/error.h
/usr/include/linux/can/error.h
/usr/include/pulse/error.h
/usr/include/soprano/error.h
/usr/src/linux-2.6.33.1-desktop-2mnb/include/config/ata/verbose/error.h
/usr/src/linux-2.6.33.1-desktop-2mnb/include/linux/can/error.h

pick one, say /usr/include/error.h and look at it and it's includes,

Here is a program I wrote to convert error number to text you could change to
print number and message.

$ cat errno.c
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>

int main (int argc, char *argv[])
{
int errnum ;

if (argc < 2)
{
printf ("\nUsage: %s error_number \n", argv[0]) ;
exit (EXIT_FAILURE) ;
}

errnum = atoi (argv[1]) ;
errno = errnum ;

printf ("%s = %s\n", argv[1], strerror (errno)) ;
exit (EXIT_SUCCESS) ;
}

Then there are the error data structures from hardware. Snippet follows:

/* error status of CAN-controller / data[1] */
#define CAN_ERR_CRTL_UNSPEC 0x00 /* unspecified */
#define CAN_ERR_CRTL_RX_OVERFLOW 0x01 /* RX buffer overflow */
#define CAN_ERR_CRTL_TX_OVERFLOW 0x02 /* TX buffer overflow */
#define CAN_ERR_CRTL_RX_WARNING 0x04 /* reached warning level for RX errors */
#define CAN_ERR_CRTL_TX_WARNING 0x08 /* reached warning level for TX errors */
#define CAN_ERR_CRTL_RX_PASSIVE 0x10 /* reached error passive status RX */
#define CAN_ERR_CRTL_TX_PASSIVE 0x20 /* reached error passive status TX */
/* (at least one error counter exceeds */
/* the protocol-defined level of 127) */

/* error in CAN protocol (type) / data[2] */
#define CAN_ERR_PROT_UNSPEC 0x00 /* unspecified */
#define CAN_ERR_PROT_BIT 0x01 /* single bit error */
#define CAN_ERR_PROT_FORM 0x02 /* frame format error */
#define CAN_ERR_PROT_STUFF 0x04 /* bit stuffing error */
#define CAN_ERR_PROT_BIT0 0x08 /* unable to send dominant bit */
#define CAN_ERR_PROT_BIT1 0x10 /* unable to send recessive bit */
#define CAN_ERR_PROT_OVERLOAD 0x20 /* bus overload */
#define CAN_ERR_PROT_ACTIVE 0x40 /* active error announcement */
#define CAN_ERR_PROT_TX 0x80 /* error occured on transmission */
From: Robert Heller on 4 Apr 2010 16:43
At Sun, 4 Apr 2010 20:16:53 +0100 markhobley(a)hotpop.donottypethisbit.com (Mark Hobley) wrote:

>
> Does anyone know of any repositories containing man pages for system error
> messages? I am looking for pages that document error messages and resolution.
>
> Manual pages for each of the error messages produced by the C library would
> be a good starting point for me. Has anyone written any such pages?
>
> I am also looking for manual pages for kernel error codes, and any application
> specific error messages, or programming environment error messages.
>
> http://markhobley.yi.org/manpages/missingman.html
>
> Mark.

man errno

>

--
Robert Heller -- Get the Deepwoods Software FireFox Toolbar!
Deepwoods Software -- Linux Installation and Administration
http://www.deepsoft.com/ -- Web Hosting, with CGI and Database
heller(a)deepsoft.com -- Contract Programming: C/C++, Tcl/Tk


From: Chris Davies on 4 Apr 2010 16:40
Mark Hobley <markhobley(a)hotpop.donottypethisbit.com> wrote:
> Does anyone know of any repositories containing man pages for system
> error messages? I am looking for pages that document error messages
> and resolution.

The resolution is often something "obvious" within the context. (No such
file or directory --> choose a different file. But I appreciate thats'
a simple one.)


> Manual pages for each of the error messages produced by the C library
> would be a good starting point for me. Has anyone written any such
> pages?

Each library call /should/ document the possible error messages that
can arise from that function's failure conditions. Intro(2) or errno(3)
on some systems may help you determine the meaning of the specific error
codes that can be raised by system calls.


> I am also looking for manual pages for kernel error codes, and any
> application specific error messages, or programming environment error
> messages.

That's an extremely wide net. You might want to start with system calls
and their documented errors. Then move on to library calls, and finally,
try to determine what error codes get generated by the particular set
of applications you have in mind.

Chris
From: despen on 4 Apr 2010 20:19
markhobley(a)hotpop.donottypethisbit.com (Mark Hobley) writes:

> Does anyone know of any repositories containing man pages for system error
> messages? I am looking for pages that document error messages and resolution.

Man pages aren't organized that way, nor should they be.

Look instead at the documentation for the APIs.

> Manual pages for each of the error messages produced by the C library would
> be a good starting point for me. Has anyone written any such pages?

Each of the APIs in libc has a man page.

> I am also looking for manual pages for kernel error codes, and any application
> specific error messages, or programming environment error messages.

Again, wrong way to go about it.

> http://markhobley.yi.org/manpages/missingman.html

How about working with an existing documentation project:

http://tldp.org/authors/
 |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11
Prev: Live CD to scan windows pc for a virus
Next: where is CentOS storing my hostname that it resets it on each reboot?