Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!sdd.hp.com!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!fauern!opal!tmpmbx!scuzzy!src
From: src@scuzzy.in-berlin.de (Heiko Blume)
Newsgroups: comp.unix.programmer
Subject: Re: Problems with signal handler
Message-ID: <1991Jan25.202024.11003@scuzzy.in-berlin.de>
Date: 25 Jan 91 20:20:24 GMT
References: <1991Jan22.151906.9695@daimi.aau.dk> <1991Jan22.230448.28521@NCoast.ORG> <1991Jan23.183422.24871@robobar.co.uk>
Organization: Contributed Software
Lines: 19

ronald@robobar.co.uk (Ronald S H Khoo) writes:
>Actually, what I'd really like to know is, is there an abstract interface to
>"held" signals that maps reasonably well on top of all the seemingly
>endless different kinds of signal interfaces ?  Or is it really the case
>that all we can really use in half-portable code is just plain signal() ?

if you mean how to find out what (blocked) signals are pending (do you?)
posix has defined such an interface:

sigset_t set;				/* this object */
sigemptyset(&set);			/* must be initialized */
sigpending(&set);			/* to be filled with the pending-set */
if(sigismember(&set,SIGCHLD))		/* and tested for a specific signal */
   printf("SIGCHLD had been posted\n");
-- 
      Heiko Blume <-+-> src@scuzzy.in-berlin.de <-+-> (+49 30) 691 88 93
                    public source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home