Clam module broken after main.cvd update

[Raymond Dijkxhoorn]

Hi!

>> Apr 11 02:38:00 vmx120 MailScanner[1037]: None of the files matched by the
>> "Monitors For ClamAV Updates" patterns exist!
>> Apr 11 02:38:05 vmx120 MailScanner[1040]: None of the files matched by the
>> "Monitors For ClamAV Updates" patterns exist!
>> Apr 11 02:38:10 vmx120 MailScanner[1062]: None of the files matched by the
>> "Monitors For ClamAV Updates" patterns exist!
>>
>> This will give defuncts on all your MS processes.
>>
>> The behaviour is only with 0.9x so be aware you will for sure see your
>> incomming queue raise till you manually fix this.
>>
>> On my system clam created dirs like:
>>
>> /usr/local/share/clamav/daily.inc
>>
>> I removed all inside /usr/local/share/clamav/ (all subdirs also) and did a
>> freshclam. Now the main.cvd remains in the main dir again and its going
>> again.
>>
>> This is most likely a temp fix till someone fixes MS to detect this. ;)
>>
>> If you see the above behaviour, or wonder why your MS is defuncting all
>> off the sudden, you know what to do....

> I've been waiting for the same behaviour but the clamav updates have been
> failing all week.  Did your clamav autoupdate install the update or did
> you do it manually?

You can wait a few MONTHS after the new main update will be released...
This aint happening with daily updates.

It wont auto fix itself or something.... its broken.

Bye,
Raymond.