[clamav-users] Clamscan taking a very long time

[Michael Newman]

> On Jan 5, 2020, at 00:00 ,G.W. Haywood wrote:
> 
> 
> Look at the 'LogVerbose' and 'Debug' directives.

The LogVerbose directive seems to do the same thing as the -v parameter with clamscan. All that does is list every file that is checked. It also tells whether or not the file is OK.

The Debug directive seems to do the same thing as the --debug parameter of clamscan. When scanning my desktop with 47 files it produced over 7000 lines of output, most of which I don't understand.

Is there no easy way to find out exactly what:

Total errors: 4

means and what those errors were?

I see that this question has been asked and not answered before:

https://superuser.com/questions/842916/clamav-shows-errors-found-but-how-to-find-out-what-they-are <https://superuser.com/questions/842916/clamav-shows-errors-found-but-how-to-find-out-what-they-are>

https://askubuntu.com/questions/295477/meaning-of-total-errors-on-result-of-clamav-scan <https://askubuntu.com/questions/295477/meaning-of-total-errors-on-result-of-clamav-scan>

So, I guess the answer is "No"


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clamav.net/pipermail/clamav-users/attachments/20200105/a12041d3/attachment.htm>