Hi,
Had no more issues after using the service file shipped with source code.
What I did was:
cp squid.service /etc/systemd/system
systemctl daemon-reload
systemctl enable squid
systemctl start squid
Alex
On Mon, Jun 11, 2018, 10:11 Eliezer Croitoru <eliezer@xxxxxxxxxxxx> 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
----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: eliezer@xxxxxxxxxxxx
-----Original Message-----
From: Amos Jeffries <squid3@xxxxxxxxxxxxx>
Sent: Monday, June 11, 2018 09:25
To: Eliezer Croitoru <eliezer@xxxxxxxxxxxx>; 'Alex K' <rightkicktech@xxxxxxxxx>
Cc: squid-users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: 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
.service.
"
# Automatically generated by systemd-sysv-generator
SourcePath=/etc/init.d/squid
"
Amos
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
