From owner-freebsd-questions Fri Apr 14 11:32:44 2000 Delivered-To: freebsd-questions@freebsd.org Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (Postfix) with ESMTP id BA7F937B5F9 for ; Fri, 14 Apr 2000 11:32:41 -0700 (PDT) (envelope-from cmascott@world.std.com) Received: from world.std.com (root@world-f.std.com [199.172.62.5]) by europe.std.com (8.9.3/8.9.3) with ESMTP id OAA20022 for ; Fri, 14 Apr 2000 14:32:40 -0400 (EDT) Received: (from cmascott@localhost) by world.std.com (8.9.3/8.9.3) id OAA16221 for freebsd-questions@freebsd.org; Fri, 14 Apr 2000 14:29:47 -0400 (EDT) Date: Fri, 14 Apr 2000 14:29:47 -0400 (EDT) From: Carl Mascott Message-Id: <200004141829.OAA16221@world.std.com> To: freebsd-questions@freebsd.org Subject: Re: FBSD3.3-R: olvwm leaves zombies Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm having a problem with FreeBSD 3.3-RELEASE that I didn't > have with 2.2.7-RELEASE. When I exit a program that I started > from my olvwm 4.2 Programs menu, if the program created a > child process, that child process becomes a zombie. I have > three programs that do this: > > Netscape Navigator 4.08 for FreeBSD; > Netscape Navigator 4.72 for FreeBSD; > An MP3 player that uses the xaudio library, FreeBSD version. > > All of these are a.out executables. > Unfortunately, source code isn't available for these, at least > not for the part that does the fork/exec. > > If I start any of these programs from a shell prompt in an > xterm window, running the program in the background, there's > no zombie after I exit the program. Please disregard the above. First, I just reproduced the problem on 2.2.7-RELEASE. Second, I discovered that all it takes to make the zombie go away is to move the mouse cursor over the root window. I guess olvwm was sleeping and the mouse event woke it up, at which time it found out about death of child. -- Carl Mascott cmascott@world.std.com uunet!world!cmascott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message