On Sun, 09 Jun 2013 20:15:14 +0300 Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote: > As you wrote there is no need for service disruption. > The old method I have used was to actually spawn a second squid while > reloading but it seems like a very messy solution. > I think that for an ISP solution there should be 0 fault tolerance > since the service should give answer to hospitals and other life > related services that should not be disrupted by an admin which > doesn't now about when and why he does the update or upgrade. > The admin should from my point of view do what ever needed for this > specific task and not rely on the split second which a miracle will > serve this small kid who the social worker is just handling now. > > I do hope my words was understood as a compliment to all the related > amazing guys who worked and works days and nights. > > Eliezer > > On 6/9/2013 7:46 PM, Squidblacklist wrote: > > On Sun, 09 Jun 2013 13:34:11 -0300 > > Marcus Kool <marcus.kool@xxxxxxxxxxxxxxx> wrote: Actually, I proposed two solutions. While the bash script is messy I will admit, the optimal solution of having a parent and child proxy is rather elegant, fault tolerant, and works without issue. The child proxy simply ignores and bypasses the parent proxy while the reload procedure is underway, and resumes passing traffic through it when it is ready to serve requests. You should try it. - Signed, Fix Nichols http://www.squidblacklist.org
