Hi there,
On Thu, 1 Oct 2020, Dave Sill via clamav-users wrote:
"G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> wrote:
It might be too soon to draw that conclusion. It's possible that the
daemon reloaded its database during your test, and I'd expect that to
cause any cached results to be discarded for obvious reasons.
Fair enough. I re-ran the same scan three times after rebooting and got
the following run times:
20:46
19:37
19:18
And the clamd logs show "SelfCheck: Database status OK" every 10 minutes
but no DB updates.
...
I only have 16 GB RAM on this system ...
Only 4GB on my clamd server.
$ du -sh images/
16G images/
$ find ./images -type f | wc -l
11586
$ clamdscan images/
...
Time: 12547.333 sec (209 m 7 s)
...
$ clamdscan images/
...
Time: 1477.782 sec (24 m 37 s)
Trying a bigger directory, this is going to take a while...
$ find ./Personal -type f | wc -l
144191
--
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
