From owner-freebsd-current@FreeBSD.ORG  Sat Dec 27 13:51:54 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 18F5D16A4CE
	for <freebsd-current@freebsd.org>;
	Sat, 27 Dec 2003 13:51:54 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B21143D3F
	for <freebsd-current@freebsd.org>;
	Sat, 27 Dec 2003 13:51:52 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id hBRLpljl001036;
	Sat, 27 Dec 2003 22:51:47 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Oliver Brandmueller <ob@e-Gitt.NET>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 27 Dec 2003 21:50:00 +0100."
             <20031227205000.GG86308@e-Gitt.NET> 
Date: Sat, 27 Dec 2003 22:51:46 +0100
Message-ID: <1035.1072561906@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: file descriptor leak in 5.2-RC 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2003 21:51:54 -0000

In message <20031227205000.GG86308@e-Gitt.NET>, Oliver Brandmueller writes:

>Do you mean, there's something in the place where a daemonized process 
>exits?

I really don't know...

The most suspect places are calls to dup(2)/dup2(2), close(2), exec(2)
[for close on exec filedescriptors], exit(2) processing and finally
filedescriptor-passing via sockets.

I have only followed this on the sideline, so I don't have all the
details at hand and I can't really say how I would go about debugging
it, probably by trying to reproduce it in single-user and then
pouring printfs all over the kernel where filedescriptors gets
created/destroyed, and try to figure out which one doesn't get there.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.