From owner-freebsd-hackers  Mon Sep  1 16:18:18 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA25704
          for hackers-outgoing; Mon, 1 Sep 1997 16:18:18 -0700 (PDT)
Received: from counterintelligence.ml.org (mdean.vip.best.com [206.86.94.101])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25698
          for <freebsd-hackers@freebsd.org>; Mon, 1 Sep 1997 16:18:13 -0700 (PDT)
Received: from localhost (jamil@localhost)
	by counterintelligence.ml.org (8.8.7/8.8.5) with SMTP id QAA02302
	for <freebsd-hackers@freebsd.org>; Mon, 1 Sep 1997 16:17:21 -0700 (PDT)
Date: Mon, 1 Sep 1997 16:17:21 -0700 (PDT)
From: "Jamil J. Weatherbee" <jamil@counterintelligence.ml.org>
To: freebsd-hackers@freebsd.org
Subject: SIGCLD
Message-ID: <Pine.BSF.3.96.970901161354.2293B-100000@counterintelligence.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I guess SIGCLD is really SIGCHLD under freebsd, no?
I was looking at a daemon skeleton out of a Stevens book on Network
programming, he specifically sets up a function that calls wait3 so that
child zombies aren't left around --- however the signal man page for
freebsd calls this SIGCLD and says that it is discarded by default which
would suggest to me that wait3() is unnecessary if you are not interested
in the status of the child.