Hi there,
On Sun, 5 Jan 2020, Michael Newman via clamav-users wrote:
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:
There was in fact an answer to the askubuntu question, even if it was
not very helpful, but both those questions were asked over five years
ago so I think they're best ignored.
So, I guess the answer is "No"
The other questions notwithstanding, your guess is incorrect unless
you meant "if I ask in the wrong place is there no easy way..."
Look at (about) lines 400-444 in clamdscan/proto.c.
I can only be approximate with those line numbers because I'm looking
at a development version of the source code at present, but if you do
take the trouble to look you will see that (1) the errors are counted
by the callbacks which do the scanning under various circumstances and
(2) when errors occur and are counted, they are also logged. So I
guess the errors that you're asking about are noted amongst the 7000+
lines of output of which you have posession. You might want to look
into some of the text processing tools available, such as 'grep'.
--
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
