Re: [squid-users] clarification of delay_initial_bucket_level

From: <tcr_at_raynersw.com>
Date: Thu, 27 Sep 2012 12:47:58 -0700

> Jenny as far as I can tell from your mail you are running a restart
> (service squid3 restart or /etc/init.d/squid3 restart) and not a
> reload, reloads in my experience are very fast, they fix almost
> everything and are close to unfelt by the users, I have had streams
> running in a browser while I reloaded and they just continued with no
> problem (but that may also be effective caching on the websites part).
> Eli

My experience corroborates this. I run some very high-traffic servers and reloads have never caused problems. If they did I would definitely hear about it. It seems Amos and the others did a good job with the conf file reloading and I don't see a reason not to use it. Frankly a modern server should be reload-able on the fly- it doesn't cause problems for apache, nginx, bind, postfix, and it shouldn't cause problems for squid either. That's why I wanted a more detailed explanation than "very bad idea" before I go uprooting a working system.

-Ty
Received on Thu Sep 27 2012 - 19:47:59 MDT

This archive was generated by hypermail 2.2.0 : Fri Sep 28 2012 - 12:00:05 MDT