What to look for in Log file?

Hello Joseph Lundstrom,

question is, are your counts correct? Might be that you've missed or interpreted some lines. Without the log it's impossible to say where the assumed discrepancy comes from.

Christian

Hello Christian,
Thank you for responding.

QC> question is, are your counts correct?

Yes counts are correct. Because :
counted Log file errors manually via Ctrl-F and
counted Log file errors via Bash Ubuntu 20.04.3 commands

snippets from Bash:

dir2=' /home/u3/Desktop/Sophos_scan.txt ' ;

cat $dir2 | grep -ioc '>>> Virus' | tr '\n' ' ' ; echo " >>> Virus"

cat $dir2 | grep --color=always 'scanned in' ;

cat $dir2 | grep -ioc '(corrupt)' | tr '\n' ' ' ; echo "(corrupt) Could not check" ;

cat $dir2 | grep -ioc '(virus scan failed)' | tr '\n' ' ' ; echo "(virus scan failed) Could not check"

etc ,,,

Said differently,
Is there a Sophos document of phrases the
program generates to make the Log file?

What are all the phrases that
Sophos might generate in a Log file?

Examples of phrases discovered thus far:
(corrupt) Could not check
(virus scan failed) Could not check
Could not open
Password protected files
appears to be a 'zip bomb' Aborted checking
>>> PUA
>>> Virus

--

Hello  Joseph Lundstrom ,

counts are correct
well,  that you get the same counts manually and with grep doesn't prove that you didn't miss certain errors.

phrases the program generates
AFAIK there is no documentation of all possible messages. Have a look at swpmess.dat that's in the same directory as sweep (the actual scanner).

Christian

QC said:

Have a look at swpmess.dat that's in the same directory as sweep (the actual scanner).

Hello  Joseph Lundstrom,

sorry, after install it's in /opt/sophos-av/lib/sav/ (in /usr/local/bin/ are only links, BTW).

Christian

Hello  Joseph Lundstrom,

sorry, after install it's in /opt/sophos-av/lib/sav/ (in /usr/local/bin/ are only links, BTW).

Christian