Andres wrote:
> On 7/23/07, Daniel J McDonald <[EMAIL PROTECTED]> wrote:
>> clamd stopped. Restart the clamd service and you should be fine.
>>
>
> Thanks Guys! I restarted clamav-daemon, the log looks fine now, I'll
> check it a while.
Actually, I don't think this will help for long and I suppose it will
happen again on the next clamd logrotate.
I noticed that if clamd is restarted, amavisd seems not be able to talk
to clamd anymore. To make thinks even worse, after a day of talting to
clamscan, amavsid seems to corrupt some of its internal Berkeley dbs.
I added a
/etc/init.d/amavisd-new restart >/dev/null
to /etc/logrotated/clamav-daemon after the reloading of clamd
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
