Am 01.02.2018 um 19:49 schrieb Chris:
I'm not sure if that's correct or not since I never had a reason to monitor the start of the clamav-daemon before. Doing more Googling I came across https://serverfault.com/questions/798587/debian-8-cant-get- clamav-to-listen-on-tcp-3310 which is somewhat like my issue. It mentions "Comment out all ListenStream= in /lib/systemd/system/clamav- daemon.socket."
why don't you just disable all the socket-activation stuff and just ordinary enable and start apure clamd-service as it is?
given that clamd needs a lot of time at startup to initialize the signatures what is the point of socket-activation at all?!
_______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
