Date: Mon, 12 Dec 2005 12:00:02 -0500 From: Robert Fitzpatrick <lists@webtent.net> To: "Michael C. Shultz" <ringworm01@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Reaching kern.maxfiles Message-ID: <1134406802.6334.33.camel@columbus.webtent.org> In-Reply-To: <200512120757.31052.ringworm01@gmail.com> References: <1134397159.6334.21.camel@columbus> <200512120757.31052.ringworm01@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2005-12-12 at 07:57 -0800, Michael C. Shultz wrote: > On Monday 12 December 2005 06:19, Robert Fitzpatrick wrote: > > Been running this FreeBSD 5.2.1 server since 5.2 was released, never had > > an issue couldn't resolve, especially with the help of this and other > > lists. Now I'm stumped. I posted this issue last week, someone suggested > > I look at: > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kern > >el-limits.html > > > > The problem with reaching kern.maxfiles started immediately after doing > > several upgrades including Perl 5.8.4 to 5.8.7 and other minor level > > upgrades - Postfix 2.2.3 to 2.2.6, amavisd-new 2.2 to 2.3, SpamAssassin > > 3.0 to 3.1 and others. Since stopping and starting Postfix every 10 > > minutes alliviates the issue, I portdowngraded Postfix, amavisd-new and > > SpamAssassin to previous packages and still reach the kern.maxfiles of > > over 12000 within minutes. > > Downgrading just a few ports doesn't take into account their dependencies, > and if you downgrade the dependencies then other ports that need them will > have problems. > No issues with my downgraded ports, but still the issue with reaching kern.maxfiles, I have located this document, could this still be related to my 5.2.1 kernel? Or, is there a way I could see if this is suspect on my system? http://www.freebsd.org/cgi/query-pr.cgi?pr=58687 -- Robert
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1134406802.6334.33.camel>