what happens if I get a too recent virus file, the engine doens't recognize it and dumps everything into infected. you say this should not happen but it did to me. here's my logs ... I had to upgrade engine before it worked again. can anyone shed some insight? thanks
ClamAV update process started at Tue Jul 8 22:15:00 2008 SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES See the FAQ at http://www.clamav.net/support/faq for an explanation. WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.91.1 Recommended version: 0.93.3 DON'T PANIC! Read http://www.clamav.net/support/faq main.inc is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven) Downloading daily-7670.cdiff [100%] Ignoring mirror 65.120.238.2 (too often connections with outdated version) ERROR: getpatch: Can't download daily-7671.cdiff from database.clamav.net Downloading daily-7671.cdiff [100%] daily.cvd updated (version: 7671, sigs: 35332, f-level: 33, builder: ccordes) WARNING: Your ClamAV installation is OUTDATED! WARNING: Current functionality level = 20, recommended = 33 DON'T PANIC! Read http://www.clamav.net/support/faq Database updated (347636 signatures) from database.clamav.net (IP: 138.123.96.134) Tomasz Kojm wrote: > On Fri, 11 Jul 2008 09:38:08 -0700 > "Julie S. Lin" <[EMAIL PROTECTED]> wrote: > > >>> so, everythings working great. I update my virus db once a day and >>> twice now run into the problem of the db file being outdated and >>> tagging everything >>> as infected. what can I do to ensure I have the least virus db (at >>> least once a day) without worrying that the application will be unable >>> to use said datafile? >>> > > The virus database is backward compatible and it will be loaded by the > old ClamAV releases, they may just not be able to use new signature formats > (which will be ignored) > > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml