|
Thanks very much for the quick response, Amos. For my use case, I would like Squid to exit when all client connections have been closed or when the timeout occurs, whichever comes first. My instances of Squid may be handling several persistent WebSocket connections, and I don't want to disrupt those. I will occasionally need to perform maintenance, so I want a safe way to stop Squid without disrupting user activity. I am using a fairly simple Squid configuration, with no caching, so I suspect that I can simply monitor the number of active Squid TCP connections using 'netstat', and then execute the second shutdown command when I detect that all those
connections are closed. I've been using the following command to count the number of active Squid TCP connections of port 443, which is the only port I use: netstat -nat | grep ".*:443.*:" | grep ESTABLISHED | wc -l That seems to give me what I want. Is it possible that bad things could happen by stopping Squid when I see that all the TCP connections have closed? Thanks. -Cody |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
