From owner-freebsd-hackers Sun Mar 2 02:55:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA04031 for hackers-outgoing; Sun, 2 Mar 1997 02:55:19 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA04025 for ; Sun, 2 Mar 1997 02:55:15 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id CAA01276; Sun, 2 Mar 1997 02:55:11 -0800 (PST) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2, 3.0 pkg_manage - where are you :-( In-reply-to: Your message of "Sun, 02 Mar 1997 09:27:44 +0100." Date: Sun, 02 Mar 1997 02:55:11 -0800 Message-ID: <1272.857300111@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > i've seen the above one time as well, due to there being many zombies > around. Apparently, sysinstall isn't very interested in the death of > its children. OTOH, it _sometimes_ is interested, and that was enough Erm, actually, if you check sysinstall's process spawning *very carefully* you will see that every child launched is waited for, and when running multi-user it's quite easy to watch the process table and see that the zombie count is not increasing. When sysinstall is running as init, it also suddenly inheirits a lot of *other* processes which it did not directly fork, and that caused us a problem until I changed the process waits to wait for anything and everything, looping until there are no more children to wait for. I'd really be surprised to see this happening again in any current version of sysinstall. Jordan