On Sun, 2012-08-26 at 23:56 +0100, G.W. Haywood wrote: > Something didn't seem quite right so I've been experimenting with > this. > ...
(1) I need to thank you very much for your time and attention. Thanks very much. (2) I need to explain why I'm running clam. I've been getting a vast quantity of spam lately; also a message bounce from a server warning me that I had sent a virus. So I want to scan my whole system for viruses, etc. The system is not a server; I run it fairly carefully and don't think I have any malware, except for a modest number of messages in some very large (too large) mail archives, most of which contain attachments which I've probably never opened, and which shouldn't have infected anything else except the small number of executables I have in ~/bin, since I always run as an ordinary user when reading my mail. Nevertheless a virus scan seems to be in order. I've run a few so far; they have all taken a very long time, mostly because I didn't realize I needed to --exclude the "system" directories /proc, /sys, and /dev. The same error has made the results very difficult to interpret. I'm running using tee because this gives me a very rough idea how the scan is coming along; a "#" option to get the same result would be better, but (hey!) I didn't write this, and shouldn't complain. For long runs like this I like to combine stdout and stderr so as to get a very rough idea which stdout lines the stderr lines refer to. Thanks again - jon _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
