Date: Fri, 24 Aug 2001 14:07:43 -0400 From: Jim Mercer <jim@reptiles.org> To: mki <mki@mozone.net> Cc: Julian Elischer <julian@elischer.org>, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: totally weirdass problem, Squid-2.3-4 and FreeBSD Message-ID: <20010824140743.T10630@reptiles.org> In-Reply-To: <20010824104400.S1286@cyclonus.mozone.net>; from mki@mozone.net on Fri, Aug 24, 2001 at 10:44:00AM -0700 References: <20010823153250.H10630@reptiles.org> <Pine.BSF.4.21.0108231746400.54256-100000@InterJet.elischer.org> <20010824131839.S10630@reptiles.org> <20010824104400.S1286@cyclonus.mozone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 24, 2001 at 10:44:00AM -0700, mki wrote: > Try recompiling squid *after* you have your local shell's ulimit's > unlimited, so that the higher limits get set by configure. > > Steps: > 1. fix up your /etc/rc.sysctl to up kern.maxfilesperproc and kern.maxfiles > 2. ulimit -n 10000 (or if in csh/tcsh, type unlimit) > * you may have to force the hardlimits up as well > 3. recompile squid (ie. rerun configure so it picks up the new values) > 4. install squid > > this should address the problems you see.. good luck.. unfortunately not. > > is there a work-around for this, other than killing/restarting squid after > > each reboot? i'm thinking maybe i should stick a "ulimit -n 10000" in the rc.d/squid.sh file. i'll have to wait for a quiet period to test (the squid is doing some 7000 hits per minute when in production). -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Now with more and longer words for your reading enjoyment. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010824140743.T10630>