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

[Roberto Carna]

Dear, my problem is that I have two different implementations of Squid
/ Dansguardian for just 40/50 users for navigation, and sometimes the
web browsing is too slow without any clue about this, it's just better
if I restart both daemons:

1) squid                          3.5.23-5+deb9u1 / dansguardian
            2.10.1.1-5.1+b4
2) squid3                             3.1.20-2.2+deb7u8   /
dansguardian                       2.10.1.1-5+b1

I've adjusted both configurations but the problem of slow navigation
appears always.

So I'm thinking maybe is a problem of this packages combination (squid
+ dansguardian)...

Do you recommend upgrade to Debian testing version packages or just to
usetry with Squid + Squidguard ??'?

Special thanks !!!

Regards.

2018-05-10 13:55 GMT-03:00 Amos Jeffries <squid3 at treenet.co.nz>:
> On 11/05/18 00:48, Roberto Carna wrote:
>> Dear Amos, thanks for your response.
>>
>> Just a short question: if I continue using my currenbt Squid version
>> with " squid.service: PID file /var/run/squid.pid not readable"
>> warning...can I have any problem or it doesn't represent any problem?
>
> It represents a problem, because systemd may interfere with the
> auto-restart built into Squid in the event of crashes etc.
>
> However, that problem wont affect normal operation, just the crash
> handling and startup/shutdown processes of Squid. So YMMV whether that
> is an issue relevant to your installation.
>
>
> HTH
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users