Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: How do you catch a signal without terminating the process ?
Keywords: SIgnal, Process
Message-ID: <16410@smoke.brl.mil>
Date: 13 Jun 91 21:25:09 GMT
References: <1991Jun5.215644.20581@csl.dl.nec.com> <1991Jun7.145102.24125@thunder.mcrcim.mcgill.edu> <1991Jun13.160901.3715@gozer.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 6

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.
Worse, SIGCHLD/SIGCLD is not even a UNIX signal, it's an abomination.