In message <[EMAIL PROTECTED]> Urban Hillebrand <[EMAIL PROTECTED]> wrote:
>We noticed as well the long delay with clamscan (several people have reported >this here). We are perfectly ok with using clamd + clamdscan - however, on >our mailgateways clamscan is still there as fallback if clamd is not >responding (due to a crash or a misconfiguration). > >With the newly introduced delays during the initialization of clamscan this >would cause us significant problems. So my question is: Will this get fixed, >or is this "working as expected"? I can't speak to whether this is "As expected" or not, but my solution was that if clamdscan reports an error and I fallback to clamscan, I only launch one instance of clamscan every 10 seconds, it scans all messages which have not yet been queued for a scan. Passes are trusted to be clean, anything which clamscan doesn't pass can sit in the queue until clamdscan recovers, since my current method doesn't let me pull individual errors out for each file without relaunching clamscan against each message individually. It's a bit of a hack, but it's the best failsafe I've come up with that doesn't slam my server. -- Dave Warren, [EMAIL PROTECTED] Office: (403) 775-1700 / (888) 300-3480 _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
