Re: Signal names with autoconf?

[Ted Zlatanov]

On Tue, 23 Apr 2002, address@hidden wrote:
> Perhaps we don't need all of the names in cfengine. I don't know
> what people will want to do. Users can just use the signal number if
> they want to anyway... One could return an error:
> 
>  "cfengine does not recognize this signal name, please use a number"
> 
> perhaps to get around this. THe simplest solution is to only support
> the most common names that are found on every unix.

Agreed, signal mappings are always a pain, and most users will not
need all of them.  I think the /bin/kill -l command will give you the
signal names in order, though.

For instance, on Linux they are "HUP INT QUIT ILL TRAP ABRT BUS FPE
KILL USR1 SEGV USR2 PIPE ALRM TERM STKFLT CHLD CONT STOP TSTP TTIN
TTOU URG XCPU XFSZ VTALRM PROF WINCH POLL PWR SYS RTMIN RTMIN+1
RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX" while on Solaris they
are "HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM
TERM USR1 USR2 CLD PWR WINCH URG POLL STOP TSTP CONT TTIN TTOU VTALRM
PROF XCPU XFSZ WAITING LWP FREEZE THAW CANCEL LOST RTMIN RTMIN+1
RTMIN+2 RTMIN+3 RTMAX-3 RTMAX-2 RTMAX-1 RTMAX".  So at the cfengine
compile time you could actually generate a header from that
information.  I know it's not ideal, but I haven't seen a Unix OS
without a working /bin/kill yet, and this gives you a clear mapping
between signal numbers and names for all the signals available.

That's how Perl does it, according to the "perldoc perlipc" man page.

Thanks
Ted