Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Dec 2003 14:51:37 -0800
From:      paul beard <paulbeard@mac.com>
To:        FreeBSD-questions <questions@Freebsd.org>
Subject:   Re: kern.maxfiles questions
Message-ID:  <64D0D128-3988-11D8-98AE-000A95BBCCF8@mac.com>
In-Reply-To: <F3510B0E-3903-11D8-98AE-000A95BBCCF8@mac.com>
References:  <F3510B0E-3903-11D8-98AE-000A95BBCCF8@mac.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Some updates to this. The machine was unresponsive this AM so I had to 
reboot it. I'm used to 90-100 day uptimes (as the power company 
permits) so this is quite unusual.

On Dec 27, 2003, at 11:03 PM, paul beard wrote:

> [/usr/home/paul]:: sysctl kern.openfiles kern.maxfiles
> kern.openfiles: 257
> kern.maxfiles: 4040
>

I raised the kern.maxfiles to 16383 and am monitoring it with mrtg 
(http://www.paulbeard.org/mrtg/red/red-openfiles.html). Already it's at 
almost 3000 (from less than 300 when I first noted it), so I assume 
I'll hit 4040 before too long.

> and on further examination I am finding some swap shortages (this 
> machine has 512 Mb of real memory but only the same amount of swap).
>

I actually only have 256 Mb of RAM with a half gig swap partition. I 
added another 512 Mb swap file and I am monitoring swap vs real mem 
usage as well (http://www.paulbeard.org/mrtg/red/red-mem.html).

if this is all I need to do, I guess that's OK, but I'm still not sure 
why it became an issue all of a sudden.

Is there some way to find out what's tying up the file descriptors?


--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?64D0D128-3988-11D8-98AE-000A95BBCCF8>