[squid-users] PID file /var/run/squid.pid not readable AND Supervising process XXX which is not our child
rightkicktech at gmail.com
Sun Jun 17 06:17:04 UTC 2018
Had no more issues after using the service file shipped with source code.
What I did was:
cp squid.service /etc/systemd/system
systemctl enable squid
systemctl start squid
On Mon, Jun 11, 2018, 10:11 Eliezer Croitoru <eliezer at ngtech.co.il> 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.
> I do not know if and when Debian Stable would upgrade their package but as
> long as you don't upgrade it automatically it would be suffice.
> Eliezer Croitoru
> Linux System Administrator
> Mobile: +972-5-28704261
> Email: eliezer at ngtech.co.il
> -----Original Message-----
> From: Amos Jeffries <squid3 at treenet.co.nz>
> Sent: Monday, June 11, 2018 09:25
> To: Eliezer Croitoru <eliezer at ngtech.co.il>; 'Alex K' <
> rightkicktech at gmail.com>
> Cc: squid-users at lists.squid-cache.org
> Subject: Re: [squid-users] PID file /var/run/squid.pid not readable AND
> Supervising process XXX which is not our child
> On 11/06/18 14:03, Eliezer Croitoru wrote:
> > Hey Alex,
> > What OS exactly is shipping this service file?
> From the first post:
> > 3.5.23-5+deb9u1
> Current Debian stable. It is not shipped exactly, but generates on
> install from the init.d file inserv headers in the absence of a shipped
> # Automatically generated by systemd-sysv-generator
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the squid-users