So "killall -HUP squid" command to parent process, permit Squid to reload
squid.conf becuase restart it, ok ?
----- Original Message -----
From: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
To: <squid-users@xxxxxxxxxxxxxxx>
Sent: Sunday, February 07, 2010 12:24 AM
Subject: Re: BUG !? swap.state: (13) Permission denied ...
Riccardo Castellani wrote:
But can I always use "killall -HUP squid" command ? I'm newby on this
Squid version.
I killed squid with killall ?!
I don't think so. killall does nasty things to the child processes inside
Squid. Best to avoid it.
You can kill -HUP the parent process by itself. Which is the same as
"squid -k shutdown", and passes the skill signal to the squid child
process after some initial cleanup.
Amos
----- Original Message ----- From: "Amos Jeffries" <squid3@xxxxxxxxxxxxx>
To: <squid-users@xxxxxxxxxxxxxxx>
Sent: Saturday, February 06, 2010 11:56 PM
Subject: Re: BUG !? swap.state: (13) Permission denied ...
Riccardo Castellani wrote:
I'm using Squid 2.7 Stable in Debian Sarge environment, when I tried to
restart Squid service but process died.
I got this message in cache.log : "swap.state: (13) Permission denied
..."
First to restart I send killall -HUP squid. What happened ?!
You killed Squid before it completed writing and setting ownership
details for the new swap.state file.
Erase the swap.state file and start Squid again as you normally would.
Have some patience this time because the startup may take a long time to
regenerate the content of swap.state from on-disk information.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE23
Current Beta Squid 3.1.0.16
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE23
Current Beta Squid 3.1.0.16
