[Clamav-devel] Why is error 13 fatal?

Mark Allan markjallan at gmail.com
Tue Oct 31 08:46:59 EDT 2017


Hi folks,

I've attached the output from 3 scans, all of which were started at root (/) with no other volumes mounted on the system.

I'm running the scans with parameters -riv (recursive, print infected only, verbose) as well as --debug.  The verbose flag prints out the name of each file being scanned, and I *believe* it prints this before attempting to start the scan of that file.

For each run, I grabbed the console output from the last "Scanning <file path>" to the end of the output.  Of particular note is Run 2, where the last line of output was the one saying which file was being scanned (prior to that point, the output was as you would expect) - no debug output at all to hint at where it went wrong.

As usual, all three scans stopped at different points.  I've tried rescanning those three files, and they all complete successfully.  Happy to send them on to you anyway if you think it would help. Just let me know where to send them - presumably they shouldn't be sent to the list?

Mark
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Run_1.txt
URL: <https://lists.clamav.net/pipermail/clamav-devel/attachments/20171031/b433805a/attachment.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Run_2.txt
URL: <https://lists.clamav.net/pipermail/clamav-devel/attachments/20171031/b433805a/attachment-0001.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Run_3.txt
URL: <https://lists.clamav.net/pipermail/clamav-devel/attachments/20171031/b433805a/attachment-0002.txt>


More information about the clamav-devel mailing list