From owner-freebsd-questions Sun Nov 19 14:34:30 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA05057 for questions-outgoing; Sun, 19 Nov 1995 14:34:30 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA05042 for ; Sun, 19 Nov 1995 14:34:23 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA01696; Sun, 19 Nov 1995 15:32:35 -0700 From: Terry Lambert Message-Id: <199511192232.PAA01696@phaeton.artisoft.com> Subject: Re: Cap'n, there be Zombies here! To: rberndt@nething.com (Randy Berndt) Date: Sun, 19 Nov 1995 15:32:35 -0700 (MST) Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <199511192122.PAA23682@vellocet.insync.net> from "Randy Berndt" at Nov 19, 95 02:28:14 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 702 Sender: owner-questions@FreeBSD.ORG Precedence: bulk > Questions: > > How does a zombie get created anyway? Each process that exits expects its parent process to ignore SIGCHLD *or* to reap it using wait, waitpid, wait3, or wait4. A child that has exited but has not been reaped by its parent is a zombie. > How can I examine a zombie to verify where it is coming from? Do a "ps -gaxl" and note its parent process ID. 8-). > Does anything in the code look wrong? Yeah. I don't see your fork so I can't tell if you are correctly ignoring SIGCHLD or reaping the child in you paren't process' main loop. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.