Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!wang!gozer!klm
From: klm@gozer.UUCP (Kevin L. McBride)
Newsgroups: comp.unix.wizards
Subject: Re: How do you catch a signal without terminating the process ?
Keywords: SIgnal, Process
Message-ID: <1991Jun25.162840.14221@gozer.UUCP>
Date: 25 Jun 91 16:28:40 GMT
References: <1991Jun7.145102.24125@thunder.mcrcim.mcgill.edu> <1991Jun13.160901.3715@gozer.UUCP> <16410@smoke.brl.mil>
Reply-To: klm@gozer.UUCP (Kevin L. McBride)
Organization: MSCG, Inc.
Lines: 19

In article <16410@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
>In article <1991Jun13.160901.3715@gozer.UUCP> klm@gozer.UUCP (Kevin L. McBride) writes:
>>Remember, never re-enable an interrupt until the condition that caused
>>the interrupt has been cleared.
>UNIX signals are not interrupts.

Yes, I am aware of this.  I was generalizing.  However, SIGCLD/SIGCHLD
behaves in this context as if it were an interrupt in that it will be
reissued immediately if not cleared before being re-enabled.

>Worse, SIGCHLD/SIGCLD is not even a UNIX signal, it's an abomination.

Agreed, albeit a useful one.

--
Kevin L. McBride    DoD      // Just say NO to the war on your freedom which,
President          #0348    //  by the way, is being fought with YOUR money.
MSCG, Inc.              \\ //   Let them know you've had enough.
uunet!wang!gozer!klm     \X/    Vote Libertarian.