since version 0.95.1 it seems the "OnOutdatedExecute" - func seems not to work anymore for freshclam ; at least with option --no-dns or when there is the WARNING: Invalid DNS reply. Falling back to HTTP mode. Reproducible: Always
I'm not sure what the old version-checking mechanism was for freshclam earlier than 0.95.2, but if you only have problems when DNS is unavailable you're seeing the expected behavior for the current freshclam design. From freshclam.conf man page: DNSDatabaseInfo STRING This directive enables database and software version checks through DNS TXT records. Default: enabled, pointing to current.cvd.clamav.net Since freshclam uses DNS queries to see what is current version for comparison against installed version, if it can't do DNS then it doesn't know to set the outdated flag. So, have you seen OnOutdatedExecute work ok when DNS _is_ available? Or does it never seem to work anymore?
(In reply to comment #1) > I'm not sure what the old version-checking mechanism was for freshclam earlier > than 0.95.2, but if you only have problems when DNS is unavailable you're > seeing the expected behavior for the current freshclam design. > > From freshclam.conf man page: > DNSDatabaseInfo STRING > This directive enables database and software version checks through DNS TXT > records. > Default: enabled, pointing to current.cvd.clamav.net > > Since freshclam uses DNS queries to see what is current version for comparison > against installed version, if it can't do DNS then it doesn't know to set the > outdated flag. > > > So, have you seen OnOutdatedExecute work ok when DNS _is_ available? Or does it > never seem to work anymore? > I can not check that, because I allways get this DNS -error, but i swa in the freshclamlog the warning that the version was outdated , only the OnOutdated-mechanism didn´t work
Ok, it seems strange that you always get a complaint about DNS. How about you attach a copy of your logfile and post output from 'emerge --info', and then we'll ask the clamav maintainers to take a look.