Bugzilla – Bug 11922
ClamDscan summary differs from clamscan summary
Last modified: 2020-11-12 02:52:06 EST
The scan summary of clamdscan and clamscan have a lot of differences. Clamscan: ----------- SCAN SUMMARY ----------- Known viruses: 6304786 Engine version: 0.99.3-beta1 Scanned directories: 257 Scanned files: 4581 Infected files: 46 Data scanned: 168.81 MB Data read: 113.33 MB (ratio 1.49:1) Time: 36.018 sec (0 m 36 s) ClamDscan: ----------- SCAN SUMMARY ----------- Infected files: 46 Time: 2.557 sec (0 m 2 s) It would be nice to easily know that clamd is actually scanning the files I assume that it is scanning. It seems odd that clamscan --recursive scans 4581 files for 36 seconds but clamd scanning the same directory for only 2 seconds. They found the same infected which is good. But, it doesn't mean that it's scanning ALL directories. We should update clamd scan summary.
Most of the missing information resides with the clamav engine and is not available to clamdscan without changing the clamd protocol. As for timing differences, clamscan time includes the time for loading the virus database where clamdscan time does not.
Also, from [clamav-users] list: Dan Rawson <drawson1@earthlink.net> 11:02 AM (37 minutes ago) to clamav-users How can I count the files/objects scanned? This works fine with clamscan ("-v --stdout -r"); I get a summary showing the number of files, etc. But when I do the same with clamdscan, all I get is: # clamdscan -v --stdout /home/drawson/Downloads/eicar.com: Eicar-Test-Signature FOUND ----------- SCAN SUMMARY ----------- Infected files: 1 Time: 1363.550 sec (22 m 43 s) I did set LogVerbose to "yes" in clamd.conf, but it didn't make any difference Thanks! Dan
Why not change the clamd protocol to be able to provide the additional information about files being scanned? I like the idea of the clamd/clamdscan very much since it saves a lot of time (because it does not load the virus database each time), BUT without the information about files being scanned clamdscan looks useless to me... I mean, I can start several instances of clamdscan to scan different files - and I have absolutely no idea which instance of clamdscan scans which file/folder and when I can expect it to be finished :(