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

Amos Jeffries squid3 at treenet.co.nz
Mon Jun 11 08:16:02 UTC 2018

On 11/06/18 19:11, Eliezer Croitoru wrote:
> It was hard for me to understand the diff\patch without the original file in plain text.
> < GuessMainPID=no
> < RemainAfterExit=no
> < PIDFile=/var/run/squid.pid
> < SuccessExitStatus=5 6
> < ExecStart=/etc/init.d/squid start
> < ExecStop=/etc/init.d/squid stop
> < ExecReload=/etc/init.d/squid reload
> The above now makes more sense but.. replacing the service file and removing the /etc/init.d/squid file should be the real way to run squid.

That assumes that systemd is going to be the init. Debian allows user
replacement of the init system with at least three to choose from. So
multiple init files need to be installed. This is just how it handles
the absence of a .service file for the newer default init while packages
transition to supporting both.


More information about the squid-users mailing list