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 -p <pid>". If you see syscalls, that's a clue on what it's doing (perhaps reading files? stuck in some loop?). Of course I assume you have checked logs already.. If you are not seeing any syscalls, debugging the process with gdb could give hints.. _______________________________________________ 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
