[ILUG] [TOTD] find error corresponding to number

[Stephen Reilly]

The \< and \> will make sure the number is surrounded by whitespace. I choose 12 in the first place to show retrieval of a subset and omision of its superset i.e. 112 didn't appear in the list. So 1 gives:

grep "\<1\>" errno.h
#define EPERM            1      /* Operation not permitted */

It would be the relevant one which contains all the #defines, not the header file with code in it. E.g. /services/kernel/kernels/linux-2.4.25/include/asm-i386/errno.h

Later,
Steve

> -----Original Message-----
> From: P at draigBrady.com [mailto:P at draigBrady.com] 
> Sent: 06 May 2004 17:10
> To: Stephen Reilly
> Cc: ilug at linux.ie
> Subject: Re: [ILUG] [TOTD] find error corresponding to number
> 
> 
> Stephen Reilly wrote:
> >>>Anyway, that's what grep is for man! :)
> >>
> >>A true believer in the Unix philosophy.
> > 
> > Too right,
> > grep "\<12\>" errno.h
> > #define ENOMEM          12      /* Out of memory */
> > Use sed if you want it formatted...
> 
> Which errno.h would that be then?
> What happens when you try 1 rather than 12?
> 
> -- 
> Pádraig Brady - http://www.pixelbeat.org
> --- Following generated by rotagator ---
> 
> Process managment
> 
> ps -A  #show all processes
> ps -Af #show all processes with full command line
> ps -Al #show all processes with extra info
> ps -A --forest  #show all processes and associated hierarchy
> 
> You can search the process list using grep, and send
> signals using the command `kill -num pid`. The default
> num is 15 (SIGTERM). `kill -l` will give a list.
> Note kill -9 should never be used in normal operation.
> --
>