|Main Archive Page > Month Archives > clamav-users archives|
On 4/29/10 7:06 AM, Adam Stephens wrote:
> That error doesn't come from the mirrors; it comes from freshclam - the
> message is in manager.c, and it's triggered by this check in mirman.c:
> if(mdat->dbflevel && (mdat->dbflevel > flevel) && (mdat->dbflevel -
> flevel > 3))
> if(time(NULL) - mdat->mirtab[i].atime < (mdat->dbflevel - flevel) * 3600)
> return 2;
> ClamAV's website says:
> "Starting from ClamAV 0.9x, whenever your ClamAV engine becomes outdated
> and the difference between the functionality level required by the CVD
> and the functionality level supported by your ClamAV engine is more than
> 3, freshclam refuses to check for updates more often than 6 times per day"
Freshclam is not necessary to use ClamAV. It is a convenience but only a minor
one. Perhaps you should decouple your system from the freshclam method and use
http. Here are the links:
Here's a way to test signature versions:
dig TXT current.cvd.clamav.net
;; ANSWER SECTION:
current.cvd.clamav.net. 900 IN TXT
The first three ":" separated numbers are the current clamav version, the
current version of the daily.cvd file, and the current version of the main.cvd
file. The fourth field is a Unix time number (Unix epoch time).
Now write a very simple script that gets the current version with dig, use curl
to download the new signatures, use clamscan to test the new signatures, and
drop them into the working directory.
This is maybe 20 lines of shell script. Take the challenge.