[squid-users] PID file /var/run/squid.pid not readable AND Supervising process XXX which is not our child

[Amos Jeffries]

On 10/05/18 11:53, Roberto Carna wrote:
> Dear, I have Squid/Dansguardian in a Debian 9 server.
> 
> My Squid packages is from Debian repo, it is the stable version:
> 
> squid                          3.5.23-5+deb9u1
...
> 
> But when I read I notice two curious lines:
> 
> systemd[1]: squid.service: PID file /var/run/squid.pid not readable
> (yet?) after start: No such file or directory
> systemd[1]: squid.service: Supervising process 895 which is not our
> child. We'll most likely not notice when it exits.
> 
> 
> Is it normal or do I have to solve these? I repeat Squid is running OK...

systemd cannot cope with daemons like Squid-3. All you can do for now is
ensure that you use the init.d scripts to manage Squid. Do not use the
"service ..." commands provided by systemd.

Squid-4 packages that resolve these issues are in Debian experimental
awaiting an official upstream stable release.
 NP: the major bugs preventing upstream stable are not affecting the
Debian package features. You can use the Squid-4 package now if you wish
by adding that "experimental" repository to your apt sources.list,
update apt, then install/upgrade Squid with "apt-get -t experimental
install squid".

Amos