> Why signal 6? signal 6 like mentioned in Aug 4 10:27:27 mybox squid[11814]: Squid Parent: child process 13220 exited due to signal 6 with status 0 Aug 4 10:27:30 mybox squid[11814]: Squid Parent: child process 14441 started Aug 4 10:27:30 mybox squid[14441]: Starting Squid Cache version 3.1.0.12-20090 kills the whole http service ? Oh really ? I thought it was a kind of graceful restart described on http://httpd.apache.org/docs/2.2/stopping.html > I don't see how wget would have surived that if it was using the > proxy.. So I probably send an SIGUSR1 during my tests... Anyway the service interruption should be very short while sending signal 6 ...? according to the log snippet approximately 3 seconds... What's about the keep-alive thing in http ? http://en.wikipedia.org/wiki/HTTP_persistent_connection Sorry I am really confused about how loadbalancers e.g. linuxvirtualserver.org are dealing with such a short service interruption. I used linuxvirtualserver.org with a connect_timeout of 5 secs. So the clients should stay connected to the same squidbox if service interruption < 5secs ? Sorry it's all a bit confusing. thanks for your advise Jan > > > > How would loadbalancers handle this behaviour ? Do they notice this > signal 6 ? > > Signal 6 forces an unexpected restart, temporarily stopping the whole > service.. very intrusive. > > > By the way is signal 6 really > > > > $ kill -l > > 6) SIGABRT ? > > Yes. > > It's much better if you use the "squid -k ..." functions to communicate > with Squid than using kill manually.. > > Regards > Henrik
