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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
