Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!hplabs!hpfcso!hpfcdc!rml
From: rml@hpfcdc.HP.COM (Bob Lenk)
Newsgroups: comp.sys.hp
Subject: Re: The future of SIGCLD.
Message-ID: <5570284@hpfcdc.HP.COM>
Date: 2 Sep 89 01:25:26 GMT
References: <173@bmers58.UUCP>
Organization: HP Ft. Collins, Co.
Lines: 12

The warning about SIGCLD originated in AT&T's System III manual.  It is
unlikely to go away in the near future.  However, the POSIX standard
defines the signal named SIGCHLD (following the Berkeley convention)
instead.  The best way to write code that will have a long, portable
life is probably to use SIGCHLD according to POSIX; in particular this
means not setting the action to SIG_IGN, but using SIG_DFL to ignore the
signal.  The name SIGCHLD is defined on series 300 releases beginning
with 6.5, and I believe on all releases of the series 800.

		Bob Lenk
		rml@hpfcla.hp.com
		hplabs!hpfcla!rml