From owner-freebsd-current@FreeBSD.ORG Fri Dec 19 02:31:11 2003 Return-Path: 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 BF62A16A4E3 for ; Fri, 19 Dec 2003 02:31:11 -0800 (PST) Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id E508743D3F for ; Fri, 19 Dec 2003 02:31:09 -0800 (PST) (envelope-from mime@traveller.cz) Received: from prg.traveller.cz (localhost [127.0.0.1]) hBJAUf8Y038541; Fri, 19 Dec 2003 11:30:41 +0100 (CET) Received: from localhost (mime@localhost)hBJAUent038538; Fri, 19 Dec 2003 11:30:41 +0100 (CET) Date: Fri, 19 Dec 2003 11:30:40 +0100 (CET) From: Michal Mertl To: Jonathan Lennox In-Reply-To: <16354.794.607812.829319@cnr.cs.columbia.edu> Message-ID: <20031219112603.O37433@prg.traveller.cz> References: <20031217110353.U94352@prg.traveller.cz> <16354.794.607812.829319@cnr.cs.columbia.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 10:31:11 -0000 On Thu, 18 Dec 2003, Jonathan Lennox wrote: > Michal Mertl writes: > > For several weeks now I see my -current (now RELENG_5_2 to help test the > > release) machine seems to be leaking file descriptors. After some time all > > files (up to kern.maxfiles) are consumed. > > Do you have any statically-linked programs that use pthreads? There's a FD > leak in gethostbyname(3) in multithreaded programs (actually, in the uthread > wrapper for kevent(2), but gethostbyname(3) is the most common reason you'd > see it) which was fixed in -CURRENT for programs linked with libc_r.so, but > not for those linked with libc_r.a. I'm afraid this is different. When your program terminates the descriptors are freed. You found a bug but it's not that serious as what I'm seeing - even when I go to single-user I see large openfiles. > > See PR bin/58687 . > This has a patch available. > > -- > Jonathan Lennox > lennox at cs dot columbia dot edu > -- Michal Mertl