On 3/13/22 19:49, Dave Blanchard wrote:
On Sun, 13 Mar 2022 18:38:05 -0400 Alex Rousskov wrote:
kill -9 will not kill SMP Squid workers and other kid
processes. To a large degree, Squid will just keep running as if nothing
happened -- that signal cannot be caught and processed specially by the
r
> "kill -9" will definitely leave some things in an odd state. Try the
> double-kill first.
On Sun, 13 Mar 2022 18:38:05 -0400
Alex Rousskov wrote:
Just to add: kill -9 will not kill SMP Squid workers and other kid
processes. To a large degree, Squid will just keep running as if nothing
hap
On Sun, 13 Mar 2022 18:38:05 -0400
Alex Rousskov wrote:
> > "kill -9" will definitely leave some things in an odd state. Try the
> > double-kill first.
>
> Just to add: kill -9 will not kill SMP Squid workers and other kid
> processes. To a large degree, Squid will just keep running as if noth
On 3/13/22 17:22, Amos Jeffries wrote:
On 14/03/22 08:48, Dave Blanchard wrote:
OK. Would there be any harm in using 'kill -9 '? 'kill '
seems to be interpreted as 'take your time, then quit whenever you're
ready.'
Indeed. Busy proxy may have many clients to finish talking to, so there
is a
On 14/03/22 08:48, Dave Blanchard wrote:
OK. Would there be any harm in using 'kill -9 '? 'kill ' seems to be
interpreted as 'take your time, then quit whenever you're ready.'
Indeed. Busy proxy may have many clients to finish talking to, so there
is a delay.
Sending the SIGHUP ('kill ') a
OK. Would there be any harm in using 'kill -9 '? 'kill ' seems to be
interpreted as 'take your time, then quit whenever you're ready.' As long as
kill -9 won't potentially cause any inconsistencies in state files or anything
like that, I guess I'll do it that way. Thanks.
--
Dave Blanchard
__
On 3/13/22 03:22, Dave Blanchard wrote:
If one has edited the config file and there is some kind of error in
the new config, 'squid -k interrupt' fails to kill Squid, but instead
complains about the broken config and exits. I think the correct
behavior should be for Squid to kill the running pro
If one has edited the config file and there is some kind of error in the new
config, 'squid -k interrupt' fails to kill Squid, but instead complains about
the broken config and exits. I think the correct behavior should be for Squid
to kill the running process regardless, then report a config er
