Hi there,
On Wed, 7 Oct 2020, Dave Sill via clamav-users wrote:
"G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> wrote:
Perhaps try enabling libclamav debug logging.
I poked around a bit and didn't see an obvious way to do that ...
You just need a line
Debug yes
in clamd.conf. There might be a "Debug no" in there already. Until
just now I've never wondered what would happen if you had both of them
in the config file, I don't think you'll want to try it. :/
Couldn't really tell where it would be logging.
It logs to the same places that clamd logs, i.e. syslog or a file
depending on LogFile and LogSyslog in clamd.conf. In the man page for
the LogFile entry it says "STRING", it might be a bit clearer if it
said /path/to/file or something like that.
One thing that did help was the -m/--multiscan option to clamdscan.
Depending on the number of cores, I've seen scans 2-5x faster.
To be expected if you use more CPU power of course. Caching should
give bigger gains, and be additional to what you get from CPU power.
... on my Fedora 32 desktop, and I see caching working great:
Ah, getting somewhere now!
So, time to test RHEL 8 and Ubuntu.
Thanks, Ged!
Please keep us posted - and you're very welcome. :)
--
73,
Ged.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
