[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Signal names
From: |
Michael Beattie |
Subject: |
Re: Signal names |
Date: |
Tue, 23 Apr 2002 12:20:45 +1200 |
User-agent: |
Mutt/1.3.28i |
On Mon, Apr 22, 2002 at 05:13:07PM -0700, Tim Auckland wrote:
> signal.h does not give you the strings for the signal names, just the
> #defines for the numbers. You have to put in a bit more work to get the
> string-to-number mapping, but it's still do-able.
>
> Something like:
...
> although there's probably a neater way.
>
> Cfengine also uses an enum somewhere in the signal name mapping code,
> which would have to be dealt with similarly.
How about just using the #define's to give the right signal, when the
name is used?
signal = hup
wherever it parses that, use SIGHUP. Then you can map symbolic names
cfengine style, to SIGxxx #define values.
I would have thought that was the sensible method.
If I sound incoherent, thats because I usually am.
Mike.
--
Michael Beattie <address@hidden>
- Signal names, Tim Auckland, 2002/04/17
- Signal names with autoconf?, Mark . Burgess, 2002/04/23
- Re: Signal names with autoconf?, Michael Beattie, 2002/04/23
- Re: Signal names with autoconf?, Mark . Burgess, 2002/04/23
- Re: Signal names with autoconf?, Michael Beattie, 2002/04/23
- Re: Signal names with autoconf?, Mark . Burgess, 2002/04/23