It's a bug. ClamAV has changed the format they use for reporting versioning.
In fact clamscan/clamdscan no longer report the "pattern file" number at
all. I'm going to have to build a new version that uses freshclam to
figure out the version number instead. Pretty minor - should have it out
nex
Using qmail-scanner-2.02. The last update of clamav and running of the
following command:
setuidgid qscand /var/qmail/bin/qmail-scanner-queue.pl -z
is not placing the clamdscan verison into qmail-scanner-queue-version.txt just
my spamassassin version. This has always worked in the past
Looks like everything is getting scanned and it works manually as
well. The QS logs are saying that scans are being completed. Don't
know why the version number of both the Clamav version and the
version of the database would not get snagged by QS.
On Feb 21, 2008, at 5:06 PM, Jim Maul wrot
Hard to say. Although both of those versions of QS should work with
that version of clamav. I was referring to MUCH older (like 1.x)
releases of QS when i mentioned it. Does clamav work correctly when run
manually?
Tim Duncan wrote:
> Just started happening after the update from ClamAV 0.92
Just started happening after the update from ClamAV 0.92 to 0.92.1
I was running 2.01st and am now running 2.02st, thinking that it
might be a version recognition thing too.
On Feb 21, 2008, at 4:54 PM, Jim Maul wrote:
> Tim Duncan wrote:
>> Hi there,
>> I just had an odd think happen and not
Tim Duncan wrote:
> Hi there,
>
> I just had an odd think happen and not sure where to go to look for
> an answer.
>
> I just went through the update for ClamAV 0.92.1 and after the update
> I did the obligatory
>
> /var/qmail/bin/qmail-scanner-queue.pl -z
>
> and now the text makes no men
Hi there,
I just had an odd think happen and not sure where to go to look for
an answer.
I just went through the update for ClamAV 0.92.1 and after the update
I did the obligatory
/var/qmail/bin/qmail-scanner-queue.pl -z
and now the text makes no mention of ClamAV Versioning like before
(
