Riccardo Castellani wrote:
I'm migrating from "Squid 2.5.STABLE3" to "Squid 2.7.STABLE3" but I noted
this point:
SQUID 2.5
There are 2 squid processes which run both as squid user:
squid 11959 1 6 May25 ? 15:44:49 (squid) -D
squid 12022 11959 0 May25 ? 00:01:38 (unlinkd)
This is a part of my squid.conf:
#cache_effective_user squid
#cache_effective_group squid
SQUID 2.7
There are 2 squid processes which run one as root user and other as squid
user:
root 3617 1 0 Jun03 ? 00:00:00 /usr/sbin/squid -D -YC
proxy 3621 3617 0 Jun03 ? 00:00:01 (squid) -D -YC
This is a part of my squid.conf:
# cache_effective_user proxy
# cache_effective_group proxy
1- In squid 2.7, can I start both processes as squid user ?
2- What behaviour is't suggested ? 2 processes which run as squid user
(Squid 2.5) or 2 processes as root+squid users (Squid 2.7) ?
You can, though its not recommended. The process you see running as root
is the master process which acts like the obsolete RunCache/RunAccel.
Its primary purpose is to monitor the other low-privilege process and
restart it if there are any problems. To maintain constant uptime from a
user viewpoint.
It's also responsible for controlling issues such as reconfiguration and
restarts happen cleanly.
I'm not sure from that info why the unlinkd is not also showing up.
I would recommend starting the master as root when using 2.7.
I'd also recommend getting rid of cache_effective_group and ensuring the
OS group privileges are correctly set for the squid user. Squid detects
them just fine these days.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15
Current Beta Squid 3.1.0.8 or 3.0.STABLE16-RC1