lukn,
Sorry about all the trouble. I wish I knew more about what was happening. I
hope it's not a legitimate bug slipping by. Let us know if you end up finding
anything else.
Regards,
Micah
On Nov 20, 2018, at 2:40 AM, lukn mailto:lukn...@gmail.com>>
wrote:
Hi Micah and Henrik
I'm slowl
Hi Micah and Henrik
I'm slowly getting to the conclusion that the old hosts are reaching EOL
which would explain the misbehaviour (just got a few unexplicable SSH
connection losses...).
grep -v '^$' clamd.conf | grep -v '^#'
LogSyslog yes
LogFacility LOG_MAIL
LogVerbose yes
TCPSocket 3310
TCPAddr
On Fri, Nov 16, 2018 at 03:52:44PM +0100, lukn wrote:
>
> However, in VMs on one host machine, clamd is idling, on the other it's
> running at 200-350% CPU (4 vcores) according to top - even when there is
> nothing to be scanned.
Usually one would investigate something this by running "strace -f
That is... bizarre. What does your clamd configuration look like?
Specifically, do you have `ScanOnAccess` enabled and set to watch specific
mount or directory paths?
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Nov 16, 2018, at 9:52 AM, lukn mailto:lukn...@gmail.com>>
wrote:
Hello list
I'm having a weird CPU hogging issue here. I'm running some servers as
VM hosts based on CentOS7 with qemu/kvm. On these I'm running various
VMs with CentOS 7 and legacy CentOS 6 (all have latest updates
installed). All of them are running clamd 0.100.2 which got installed
from a self c
