Hi there, On Tue, 23 Feb 2021, Joe Acquisto-j4 wrote:
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).
This isn't about clamav-milter, it's about your system and the way it does things. Try reading some of the the systemd 'man' pages, e.g. man systemctl man systemd.socket man systemd.syntax and if that doesn't help search for something like systemctl unit files with which you will probably need to get used to tinkering. If you have 'locate' on your system you could also try locate .socket | grep clam which might find your clamav-milter systemd .socket file. I admit (profess?) I much prefer to do things like this myself, rather than have something like systemd do it for me, but it seems to be The Way Of The World at the moment. -- 73, Ged. _______________________________________________ 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
