From owner-freebsd-questions Wed May 27 13:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28583 for freebsd-questions-outgoing; Wed, 27 May 1998 13:59:58 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28434 for ; Wed, 27 May 1998 13:59:08 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.8/8.8.8) with SMTP id NAA02254; Wed, 27 May 1998 13:58:53 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 27 May 1998 13:58:53 -0700 (PDT) From: Doug White Reply-To: Doug White To: Dean Hollister cc: FreeBSD Questions Subject: Re: Killing zombie processes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 May 1998, Dean Hollister wrote: > On Tue, 26 May 1998, Doug White wrote: > > > Fix the offending program that zombie-ing. Add a wait() call just before > > it exits to reap the children. > > Hmmm, how would you achieve this on a serial port, running a sh or bash > process? Use vi to edit the bash source & rebuild it. This is a source-level function call, not a command, thus the parens() to hint it's a function call. If bash doesn't wait then it's a bug in bash. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message