Thanks for the pointer. It's similar, but not quite the same, in that the problems I have are with the main and daily cvd files. I am not a scripter by any stretch of the imagination, but..
Is there someway I could do the same with main.cvd and daily.cvd? What I mean is, would it be possible to modify freshclam so that when databases are downloaded, it puts them in a tmp dir, runs the MD5 check, and if it fails, NOT move them into the database directory, not notify CLAMD and deletes the files? Basically what I want to do is check to see if there are new databases if so, download to /tmp/clamtmp (for example) MD5 verify the new download in /tmp/clamtmp If good, move into the proper database dir and notify clamd (default behaviour for me). If bad, do nothing but delete the corrupt cvd. This process would then repeat itself the next time freshclam runs. This way I could ensure only GOOD .cvd files get set up, and clamav won't die on me regularly Thanks for the help... On 12/12/06, G.W. Haywood <[EMAIL PROTECTED]> wrote:
Hi there, On Tue, 12 Dec 2006 Edward Dam wrote: > Intermittently, freshclam would die with an MD5 verification error Does this very recent thread help at all? Error (Cannot connect to 'localhost:3310': IO::Socket::INET: connect: Connection refused ) -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
