From owner-freebsd-questions@FreeBSD.ORG Tue Apr 26 19:37:15 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4380716A4CE for ; Tue, 26 Apr 2005 19:37:15 +0000 (GMT) Received: from mail24.sea5.speakeasy.net (mail24.sea5.speakeasy.net [69.17.117.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AD7043D5F for ; Tue, 26 Apr 2005 19:37:14 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 25954 invoked from network); 26 Apr 2005 19:37:13 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail24.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 Apr 2005 19:37:13 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 733E630; Tue, 26 Apr 2005 15:37:12 -0400 (EDT) Sender: lowell@be-well.ilk.org To: "Lauri Anteploon / ctrl-L" To: freebsd-questions@freebsd.org References: From: Lowell Gilbert Date: 26 Apr 2005 15:37:12 -0400 In-Reply-To: Message-ID: <44acnlnxcn.fsf@be-well.ilk.org> Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: kern.openfiles X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2005 19:37:15 -0000 "Lauri Anteploon / ctrl-L" writes: > I'm running FreeBSD 5.3-Release, with apache2, php5, icecast2 and sc_nsv. > To my understanding some process is eating up the file handles (over couple > of days the kern.openfiles has gone from 170 to 1700). Sooner or later this > will result in "kernel: kern.maxfiles limit exceeded" errors. > Is there a way to see wich application is holding most of these file handles > and not releasing them? You are looking for fstat(1). There are some clever scripts around for making use of the output, but I find that sort(1) is usually enough to help me quickly find a file hog.