On 19.12.17 12:28, Dan Rawson wrote:
"clamscan -v --stdout -r" and "clamdscan -v --stdout" take approximately the same time. They both use all of a single core on my quad-core machine (25% of the available CPU cycles).
as expected.
Running "clamdscan -m -v --stdout" completes in approximately 1/4 the time, but it uses essentially 100% of my available CPU cycles.
of course - that's what is it supposed to do.
Even starting the file manager took 20 or 30 seconds with that scan running.
you have 4 threads using CPU cycles and doing hard I/O, which is probably limiting factor. Maybe used RAM too... you can reduce number of clamd threads running by using option MaxThreads in clamd.conf and see how much it helps. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. - Holmes, what kind of school did you study to be a detective? - Elementary, Watson. -- Daffy Duck & Porky Pig _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net 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
