return codes and their meanings

[Jacques Carriere]

Do anyone know where I can get a description for return codes such as
rc=127
rc=26
rc=27
rc=22
rc=139
rc-21
etc,...
thanks,

Jacques

[T G Manikandan]

/usr/include/sys/errno.h

[Ganesan R]

Hi Jacques,

Refer this thread. James has explained here.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=86561

[Jacques Carriere]

TG,

How do I get the explanation for each code?

Jacques

[Duncan Edmonstone]

errno.h maps the error numbers to their defined names

man errno

will give you a brief description of what that defined name means.

Be aware that these are *system* error numbers which are pretty consistently returned by system calls. There's nothing anywhere that states that anything thats not a system call has to stick tyo these return codes. Applications and scripts can pretty much return whatever error number they like, and you have to check the documentation for each to know. The only standard I know of is the "de-facto" strandard that 0 = success and non-zero = failure.

HTH

Duncan

[Dennis Handly]

>Duncan: The only standard I know of is the "de-facto" standard that 0 = success and non-zero = failure.

Right. But 139 means the process terminated with signal 11 (139-128).

[Jacques Carriere]

I just discovered that I can use the command

grep "rc code" /usr/include/sys/errno.h such as grep 12 /usr/include/sys/errno.h
#define ENOMEM 12 /* Not enough core */

[Jacques Carriere]

merci beaucoup!

Jacques