From owner-freebsd-current Mon Oct 21 14:16:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1BCC37B404 for ; Mon, 21 Oct 2002 14:16:24 -0700 (PDT) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBF0D43E6A for ; Mon, 21 Oct 2002 14:16:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0018.cvx40-bradley.dialup.earthlink.net ([216.244.42.18] helo=mindspring.com) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 183juJ-0001nC-00; Mon, 21 Oct 2002 14:16:15 -0700 Message-ID: <3DB46E3B.36318CC6@mindspring.com> Date: Mon, 21 Oct 2002 14:14:35 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: Duncan Barclay , current Subject: Re: zombies from linux binaries References: <3DB46D21.2050807@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lars Eggert wrote: > > >I've been running the guidescope web ad blocker > > >(http://www.guidescope.com/home/) as a Linux binary under FreeBSD for a > > >long time. The thing seems to fork a child for each web request it > > proxies. > > > > > >Under -current, it seems that the child processes become zombies, and > > >the proxy stops working once 1024 or so accumulate. The zombies don't go > > >away when parent process finishes, they stick around until reboot. > > > > Is this http://www.freebsd.org/cgi/query-pr.cgi?pr=42457 related? It > > is for stable but I belive that the same behaviour is present in -current > > and it may manifest itself differently. > > I have finally applied your patch from the PR, but unfortunately it does > not fix the problem with guidescope I am seeing. Looks like something > else is broken WRT Linux forking: Linux has the SVR4 behaviour in that, if SIGCHLD is not caught, zombies are reaped automatically, without the parent needing to explicitly reap their exit status. Most likely, they are installing a signal handler of SIG_IGN for SIGCHLD, and expecting the standard behaviour for auto-reaping. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message