From owner-freebsd-hackers Fri Aug 24 10:16:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.reptiles.org (mail.reptiles.org [198.96.117.157]) by hub.freebsd.org (Postfix) with ESMTP id 9900237B40B; Fri, 24 Aug 2001 10:16:07 -0700 (PDT) (envelope-from jim@reptiles.org) Received: from localhost (1885 bytes) by mail.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Fri, 24 Aug 2001 13:18:39 -0400 (EDT) (Smail-3.2.0.111 2000-Feb-17 #2 built 2001-Apr-13) Date: Fri, 24 Aug 2001 13:18:39 -0400 From: Jim Mercer To: Julian Elischer 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> References: <20010823153250.H10630@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Thu, Aug 23, 2001 at 05:47:19PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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-hackers" in the body of the message