Hi there, On Mon, 14 Jun 2021, Lee, Raymond via clamav-users wrote:
I've been having trouble with using clamdscan to scan my entire system ...
Then don't do it! There are lots of things in Unix-like filesystems (and Linux is a kind of Unix) which should not be scanned with ClamAV. Unix exposes a lot of things to the file system which are not files. You might cause problems by scanning them. For much of the filesystem, scanning it is completely pointless. Much of what is logged for example is simply harmless text, and it would be far more useful to read it yourself than to scan it with ClamAV. You'll find some discussion about it in the mailing list archives, and also mention of things like SELinux and AppArmor. Please look there. It's no use just throwing a scanner at a system and hoping for the best. You need to develop a reasoned approach and a plan. If you don't, you might be a bigger threat to the system than the threats from which you think you're trying to protect it. -- 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
