Seems starting or restarting clamav-milter (systemctl restart clamav-milter.service)
changes owner and group of /var/run/clamav-milter.socket to root which make the
socket inaccessible to postfix (at least).
I found some reference to a similar concern dated 2009 and 2013.
Does not appear related, directly, to the start script, which appears to basically
just invoke the clamav-milter
binary.
joe a.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
changes owner and group of /var/run/clamav-milter.socket to root which make the
socket inaccessible to postfix (at least).
I found some reference to a similar concern dated 2009 and 2013.
Does not appear related, directly, to the start script, which appears to basically
just invoke the clamav-milter
binary.
joe a.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml