Re: [clamav-users] ClamAV 0.100.1 - clamd signal 11, leaves unix domain socket behind?

2018-09-19 Thread Micah Snyder (micasnyd)
Alternatively, you could switch your clamd.conf to use a TCP Socket. Just make sure it isn't internet accessible. Micah Snyder ClamAV Development Talos Cisco Systems, Inc. On Sep 19, 2018, at 12:28 PM, G.W. Haywood mailto:cla...@jubileegroup.co.uk>> wrote: Hi there, On Wed, 19 Sep 2018, Ka

Re: [clamav-users] ClamAV 0.100.1 - clamd signal 11, leaves unix domain socket behind?

2018-09-19 Thread G.W. Haywood
Hi there, On Wed, 19 Sep 2018, Karl Pielorz wrote: Is there any way to have the socket removed when clamd dies? (i.e. even due to a signal/failure?) I do things like this with ad-hoc watchdog scripts running from cron. You could write a shell script, called from cron every few minutes or so,

[clamav-users] ClamAV 0.100.1 - clamd signal 11, leaves unix domain socket behind?

2018-09-19 Thread Karl Pielorz
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 1