I'm using exim-exiscan-clamav combination on a Solaris 8 box running as MTA that handles about 100000 mail daily.
Sometimes clamd just stops for unknown reason. The process is simply gone, and then exiscan would complain "could not connect to clamd socket".
Yesterday I updated clamav from clamav-20030403 to clamav-20030424 and change some settings in clamav.conf file :
MaxConnectionQueueLength 64 MaxThreads 128
It seems to be working fine now.
I used LogVerbose, but the problem is clamd did not (and still don't) log the reason it shuts down.
Is there any plan to include LogDebug (or something like that) that will log (nearly) everything?
Regards,
Fajar
------------------------------------------------------------------------------------------------
You can verify the authenticity of this message within 7 days since delivery date at http://public-smtp.idc.plasa.com/mail_user/[EMAIL PROTECTED]&message_id=19AhG3-0003Xk-00
------------------------------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
