On Thu, Aug 23, 2001 at 05:47:19PM -0700, Julian Elischer wrote:
> the paranoid answer is that someone is replacing your squid and rebooting
> the system to cover their tracks...
you might think that, however, i'm not that paranoid.
in any case, i think i've nailed down the problem.
the wierd bit was that if i did a "squid -k shutdown" and let the wrapper
script fire it back up, it would not see the sysctl up'd values.
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?
--
[ Jim Mercer [EMAIL PROTECTED] +1 416 410-5633 ]
[ Now with more and longer words for your reading enjoyment. ]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
