I tried scanning /sys, and it gave me the same messages, but I don't
think it's a bug per se. It's more likely because /sys is a 'virtual'
directory, and it has a lot of special files, clamscan gets confused
while scanning it. If you run 'top', you'll see that clamscan is indeed
working hard to scan some of those file (like 99-100% CPU usage for
clamscan process).
You could try excluding /sys (and possibly /dev ?) from scanning with
the command-line option:
--exclude=REGEX, --exclude-dir=REGEX
Don't scan file/directory names matching regular expression.
These options can be used multiple times.
See if this helps.
--
clamAV's scan stop on /sys dir.
https://bugs.launchpad.net/bugs/644097
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
