From owner-freebsd-questions Thu Apr 13 17:35:10 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 977DC37B596 for ; Thu, 13 Apr 2000 17:35:08 -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 UAA12230 for ; Thu, 13 Apr 2000 20:35:06 -0400 (EDT) Received: (from cmascott@localhost) by world.std.com (8.9.3/8.9.3) id UAA22091 for freebsd-questions@freebsd.org; Thu, 13 Apr 2000 20:34:02 -0400 (EDT) Date: Thu, 13 Apr 2000 20:34:02 -0400 (EDT) From: Carl Mascott Message-Id: <200004140034.UAA22091@world.std.com> To: freebsd-questions@freebsd.org Subject: FBSD 3.3-R: progs started from olvwm menu leave 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. Is this a bug in FreeBSD 3.3? A bug in olvwm 4.2? A "bad interaction" between the two? Have there been any changes in signals/process groups between 2.2.7 and 3.3? Please e-mail me directly: I'm not subscribed to this list. Thanks. -- 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