Hello,
I did strike this in three boxes. Straight upgrade but opted not to touch
config when asked. Don't know if it matters. However I did not find any
reference to /etc/systemd/system/clamav-daemon.service.d/extend.conf in the
package scripts as in stretch.
The chown did make the difference. And the extend.conf prior to the upgrade
on further two boxes got the upgrade working, AFAICT.
Regards,
Filipe
On October 12, 2019 17:32:36 Hugo Lefeuvre <h...@debian.org> wrote:
Hi,
I did not notice this bug during my tests. I have just tried to reproduce
it by upgrading a jessie system from 0.100.3+dfsg-0+deb8u1 to
0.101.4+dfsg-0+deb8u1 and did not experience any issue restarting
clamav-daemon.
Furthermore, /var/run/clamav/ belonging to root:root or clamav:root does
not seem to change anything on my system. My understanding is that
/var/run/clamav/clamd.ctl is created by systemd, not by the daemon itself.
Also, I don't think chown clamav /var/run/clamav should survive a restart.
Filipe: did you also experience this bug?
Thanks.
regards,
Hugo
--
Hugo Lefeuvre (hle) | www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C
--
filipe.fons...@farmingbits.com
+351.914593743
