On Thu, 2005-01-20 at 10:47, Odhiambo Washington wrote: > > Thanks for that. Looks like that is what was causing my problems with > clamd!! I will monitor to see the behaviour. I am running CVS code of > today> > Are there other tune-ups that can be applied to clamd on a very busy > server?
As usual, it depends on what the bottleneck is with your hardware. You can tune the thread settings to the number of CPUs and the amount of concurrent traffic you get. The most likely bottleneck will be I/O. If you've got lots of spare memory you could but the clam TMPDIR on a RAM disk. Or you could improve things by having it on a dedicated disk, and tune the filesystem for fast throughput (no atime, no journalling). To be honest, ClamAV is unlikely to be a problem unless you are handling millions of messages a day. How many are you doing? -trog
signature.asc
Description: This is a digitally signed message part
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
