On Monday, May 18 2020, I wrote:

> Just a few more details I've been able to gather this afternoon.
>
> I'm using a Debian sid VM where I installed sysvinit to replace systemd.
> I wasn't able to reproduce the problem reported above, even after
> activating the apparmor profile before upgrading.
>
> If you look at the /etc/init.d/squid script, you can see that the
> startup function does create the /run/squid/ directory.
>
> I will need more info to investigate this bug.

I submitted
https://salsa.debian.org/squid-team/squid/-/merge_requests/13 to fix the
latent bug that I am experiencing when upgrading to the latest squid
(unstable) and when the apparmor profile is enabled.

It seems to me that the MR above might also fix the problem you're
seeing.  I can provide a .deb for you to test, if you're interested.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

Attachment: signature.asc
Description: PGP signature

Reply via email to