Noel Jones schrieb: > Make sure your amavisd.conf defines clamscan as a secondary > scanner. If clamd is unavailable then amavsid-new will continue to > process mail using clamscan to check for viruses. When using > clamscan, system load will increase and throughput will decrease, but > mail will still be processed. If clamscan fails too, no mail will > pass through, which is good. It is possible to configure > amavisd-new to pass mail unscanned if that's what you want, but that > is not recommended. > This is a good idea, did not think of this possibility yet.. > Use some sort of monitor to check if clamd (and other critical > processes) are running, and restart them if necessary. I like monit > because it's simple and flexible, but there are lots of other choices. > Here, monit restarted clamd a couple times on several servers last > night because of the update problems. Everything was running > smoothly when I arrived this morning. > I had something like this in mind, but did not find the time yet. > Yes, clamd and the whole clamav structure should be more resistant to > failure. Your choices are to either work with it as is, or wait > until clamav is more mature. > It should not be too hard to rewrite freshclam so it downloads the update to a temporary file first, and then processes the database. Then there would be no problem about network speed and 0.8-clients wasting bandwith. If freshclam works already like this, then I cannot understand why clamd died cause of a lock-failure.
And another point is: I got an email about problems updating with freshclam. Ok so far. But why on hell is there no mail indicating that clamd cannot open its database?? (Perhaps because my mailsystem was down at this point^^) I do not like email passing my system unscanned, but scanned with a database not up to date is better than no mail passing the system. (By the way: this would be the same thing as restarting clamd after the crash, because clamd rereads the database every hour, doesnt it.) I do not blame clamav for mail not passing, but I would like to inform the developers that there is a problem. Ok, I could have solved it by monitoring clamd, but this crash was an unnecessary one. In addition, it is not acceptable to say: "Ok, almost every clamd out there died cause of this update, but the problem are the users with clamav 0.8" I have 0.9, and I dislike to see my clamd fucked up with every update.. But to this point, great antivirus software :-) _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
