Date: Fri, 24 Aug 2001 10:44:00 -0700 From: mki <mki@mozone.net> To: Jim Mercer <jim@reptiles.org> 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: <20010824104400.S1286@cyclonus.mozone.net> In-Reply-To: <20010824131839.S10630@reptiles.org>; from jim@reptiles.org on Fri, Aug 24, 2001 at 01:18:39PM -0400 References: <20010823153250.H10630@reptiles.org> <Pine.BSF.4.21.0108231746400.54256-100000@InterJet.elischer.org> <20010824131839.S10630@reptiles.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.. -mohan On Fri, Aug 24, 2001 at 01:18:39PM -0400, Jim Mercer wrote: > this is because we have: > > /etc/rc (with default limits) > /etc/rc.sysclt (ups some of the limits) > /usr/local/etc/rc.d/squid.sh (inherits /etc/rc limits) > /usr/local/bin/RunCache (squid wrapper, inherits rc.d/squid.sh limits) > /usr/local/sbin/squid (inherits RunCache limits) > > so, if i just kill squid, it re-ineherits the limits effectively from /etc/rc. > > if i kill RunCache and squid, then restart, it gets the sysctl.conf limits. > > is there a work-around for this, other than killing/restarting squid after > each reboot? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010824104400.S1286>