Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Dec 2003 22:51:46 +0100
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Oliver Brandmueller <ob@e-Gitt.NET>
Cc:        freebsd-current@freebsd.org
Subject:   Re: file descriptor leak in 5.2-RC 
Message-ID:  <1035.1072561906@critter.freebsd.dk>
In-Reply-To: Your message of "Sat, 27 Dec 2003 21:50:00 %2B0100." <20031227205000.GG86308@e-Gitt.NET> 

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1035.1072561906>