From owner-freebsd-questions Thu Jun 27 10:28:45 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA12100 for questions-outgoing; Thu, 27 Jun 1996 10:28:45 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA12095 for ; Thu, 27 Jun 1996 10:28:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05241; Thu, 27 Jun 1996 10:27:40 -0700 From: Terry Lambert Message-Id: <199606271727.KAA05241@phaeton.artisoft.com> Subject: Re: trouble for process to be terminated To: info@adn.edu.ph (Information Help Desk) Date: Thu, 27 Jun 1996 10:27:39 -0700 (MST) Cc: freebsd-questions@freebsd.org In-Reply-To: from "Information Help Desk" at Jun 27, 96 01:58:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What's the last resort besides rebooting after killing a process > that still lives but is trying to exit? Use "ps" to determine the resource it is blocking on. The free up the resource. The _exit will complete, and the process will exit. Most likely, the process which forked the zombie process has not called "wait" like it should to reap the return value from the process exit. If the process is not able to call "wait", it should ingnore SIGCHLD to allow the process to be reaped automatically. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.