Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: SIGCONT occurs after a SIGTERM
Message-ID: <10007@dog.ee.lbl.gov>
Date: 18 Feb 91 10:43:02 GMT
References: <7103@fs1.cam.nist.gov> <67880001@hpcupt1.cup.hp.com> <2519@inews.intel.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 15
X-Local-Date: Mon, 18 Feb 91 02:43:02 PST

In article <2519@inews.intel.com> bhoughto@pima.intel.com
(Blair P. Houghton) writes:
>Not the least of those variances is that signals may be queued ....

Signals are not queued.

As far as I know, there is only one piece of one Unix manual that
claims otherwise (that being the System V SIGCLD documentation), and it
lies.  Signals are never queued.  System V SIGCLD signals use a
different trick that causes properly-coded wait routines to be called
once per exited child, but which causes improperly-coded wait routines
to recurse indefinitely.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov