Hi,
I'm running ClamAV 0.100.1 (from pkg) under FreeBSD 11.2 amd64 -
occasionally it's being passed something it doesn't like, and 'clamd' is
dieing with a signal 11, i.e.
Sep 19 10:34:50 host clamd[855]: SelfCheck: Database status OK.
...
Sep 19 10:35:27 host kernel: pid 855 (clamd), uid 106: exited on signal 11
I'm trying to track down what content is causing this.
Software connects to clamd via a local unix domain socket, e.g.
'/var/run/clamav/clamd.sock'. If clamd dies - this socket is left behind,
and software still blindly connects to it.
Is there any way to have the socket removed when clamd dies? (i.e. even due
to a signal/failure?)
Having it still there (e.g. 'telnet -u /var/run/clamav/clamd.sock' still
connects) causes processes to backup - as they patiently wait for a daemon
that's sadly long gone.
Thanks,
-Kp
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
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
