Skip site navigation (1)Skip section navigation (2)
Date:      26 Apr 2005 15:37:12 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: kern.openfiles
Message-ID:  <44acnlnxcn.fsf@be-well.ilk.org>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAraBMZwunwUCj0cCUC/kKUsKAAAAQAAAAznpt/Nn2ZE6W1EBrQLt2egEAAAAA@bitifarm.ee>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAraBMZwunwUCj0cCUC/kKUsKAAAAQAAAAznpt/Nn2ZE6W1EBrQLt2egEAAAAA@bitifarm.ee>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
"Lauri Anteploon / ctrl-L" <lauri@bitifarm.ee> 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.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?44acnlnxcn.fsf>