Re: squid -k reconfigure does not work with cache_effective_user on 3.1.0.17

Jenny Lee wrote:
> Hello all,
>
> No matter what I do, I cannot get squid reload with 3.1.0.15.
>
> Directory permissions and everything is properly set for cache_effective_user. Squid starts at boot with initscripts, opens a low-numbered port. It works fine when run as root, and switches to cache_effective_user as expected (child and spawn nsca_auth processes).
>
> However, I cannot send it a reconfigure signal with 'squid -k reconfigure' or 'kill -HUP'... when i am logged in as cache_effective_user.
>
> I can send a kill signal to apache for example (running under the same uid).
>
> ERROR: Could not send signal 1 to process 7467: (1) Operation not permitted
>
> RHEL 5.4 x64
> SELinux disabled
>
>
> I tried setuid /bin/kill but that did not work either.
>
> This was working fine before with 2.6. Any ideas how to reload squid or what happenned?
>
> Thanks!
>
> J
>
> PS: Same issue with 3.1.0.17 too.

Sounds like its working.

The master process which receives signals and does special operations is
running at a higher privilege level than the cache_effective_user.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE7 or 3.0.STABLE24
   Current Beta Squid 3.1.0.17