|
Terry, Maybe if you could clarify. You are running ClamAV in daemon mode, am I correct? My point was that as of several months ago, the non-daemon installation was a processor hog and took a lot of time compared to F-Prot, the best performing scanner. Things might have changed since then. I also noted that when run in daemon mode, ClamAV was virtually as fast as F-Prot, and used less resources. I'm not running ClamAV because I had issues with the stability/management of their daemon at that time. I suspect that things have changed since then. Regardless, I would not be surprised to see the per-process launched ClamAV causing excessive load on a busy server. It wasn't clear if John was running one way or another. Hitting a 60 second timeout suggests that his server was being redlined for a prolonged period of time, and going to the daemon mode might provide substantial relief. If his other scanner isn't F-Prot, he should also think about switching because there is nothing as efficient as F-Prot, and it hardly uses any resources. Matt Terry Fritts wrote: ClamAV when not run in daemon mode is very slow in comparison to other virus scanners. If your server is getting pushed to it's limits, the first sign will likely be their vir directories piling up as a result of ClamAV not finishing within the specified time configured in Declude Virus. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== |
- [Declude.Virus] ClamAV scan time John Carter
- Re: [Declude.Virus] ClamAV scan time Matt
- Re: [Declude.Virus] ClamAV scan time Terry Fritts
- RE: [Declude.Virus] ClamAV scan time Matt
- RE: [Declude.Virus] ClamAV scan time John Carter
- Re: [Declude.Virus] ClamAV scan time Nick
- Re: [Declude.Virus] ClamAV scan time Scott Fisher
