On 2/10/2016 2:08 p.m., Benjamin E. Nichols wrote: > I wouldnt advise reconfigure for when you update your blacklists, sure > it sounds great, but in reality, as I said, in my experience, only > sometimes will it actually reload the acl from disk, sometimes it wont. > Youll do a reconfigure and discover your squid is still running the old > acls which presumably are memory resident, now this may have been a bug > thats been since fixed, but Im not messing with it. In our testig > environment we dont have time to be dealing with squid deciding to load > an acl from disk when it feels like it should do so, we need it to load > from disk every time. > > Once you do your own testing youll see what im talking about, go ahead > and add some urls to your acl and -k reconfigure, do this a few times, So you are sening Squid a series of reload signals so fast it does not have time to complete one before the next is arriving? There are many fixes in Squid-4 and latest 3.5 for those situations. But still some open bug reports about the behaviour there. Those are not related to ACLs specifically. Any reconfig task that takes longer than the time between -k reconfigure signals being sent will trigger issues. ... Ironically using a helper is one of the things which breaks. Squid looses track of whether any given new helper being started was for the current or previous -k reconfigure signal. And of course connections and transactions which are already underway are not affected by newly loaded config details. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
