Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!hplabs!hpda!hpcupt1!hpisod2!decot
From: decot@hpisod2.HP.COM (Dave Decot)
Newsgroups: comp.sys.hp
Subject: Re: The future of SIGCLD.
Message-ID: <16710018@hpisod2.HP.COM>
Date: 1 Sep 89 23:51:02 GMT
References: <173@bmers58.UUCP>
Organization: Hewlett Packard, Cupertino
Lines: 12

> HP-UX documentation says that SIGCLD should not be used as it may be
> removed in some future release. Is this really true? It is the only
> asynchronous way to detect the death of a child process and really is
> extremely useful. If it is going to be removed then when, and what are
> the suggested alternatives?

I suppose they should use SIGCHLD instead, since that is required by
POSIX, and SIGCLD isn't.

Perhaps we should say that.

Dave