Paul Kosinski wrote:
Needless to say, I can not do daily scans of all files with ClamAV on my new file server. Even if CPU weren't always pegged at 99-100%, a daily elapsed time of far more than 24 hours doesn't work on this planet. (And no, I can't afford to get a super-fast quad-CPU Opteron box, especially since the proof-of-concept Samba server was almost as fast at serving files even though it was only 650 MHz.) I would appreciate any suggestions. P.S. Amazingly, Windows 98 SE is quite stable as a file server -- if you don't run applications, uptimes of 30, 60 or even 90 days are not difficult.
Don't scan every file every day - that makes no sense. Just scan files that have changed since the previous scan (google tripwire and similar tools).
FWIW I differentially scan a multi-terrabyte (50 t to be exact) file system in just over a couple hours with clamav. The first time I scanned it required a couple weeks.
BTW, I had a scanner that didn't do a full file scan and I got rid of it too - good choice.
You didn't say what your iowait rate was during your scan (from top, for example). If you have multiple disks/arrays you can also fire off multiple scanning sessions as I doubt you're pegging the cpu's. This doesn't work well if you're on a set of mirrored disks.
dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
