Date: Fri, 24 Aug 2001 13:18:39 -0400 From: Jim Mercer <jim@reptiles.org> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: totally weirdass problem, Squid-2.3-4 and FreeBSD Message-ID: <20010824131839.S10630@reptiles.org> In-Reply-To: <Pine.BSF.4.21.0108231746400.54256-100000@InterJet.elischer.org>; from julian@elischer.org on Thu, Aug 23, 2001 at 05:47:19PM -0700 References: <20010823153250.H10630@reptiles.org> <Pine.BSF.4.21.0108231746400.54256-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010824131839.S10630>