Bob wrote:
> On Thursday 29 Sep 2005 12:08, Don Levey wrote:
>> [EMAIL PROTECTED] wrote:
>>> On 9/28/05, Don Levey <[EMAIL PROTECTED]> wrote:
>>>> [EMAIL PROTECTED] wrote:
>>>>> And clamd -V reports what?
>>>>
>>>> That gives me 0.87, just like the others.
>>>> I didn't kill (or restart) any of the clam processes when I
>>>> upgraded, but previous upgrades stopped/started the processes as
>>>> part of the installation (I install from RPM). I only see
>>>> freshclam as a running process; I run clamav-milter and sendmail,
>>>> which otherwise has worked well for me.
>>>
>>> It is a bug in logwatch. If you do not logrotate daily then the
>>> logwatch scriptlet for clamav will flag that no matter how long in
>>> the past. I havent had time to try and find a fix.
>>
>> Ah, I see - so it's not really a problem with the versions per se.
>> When the logs rotate again, will it clear up?
>
> have a look in /var/log/freshclam.log and see what it says there. If
> it is reporting 0.87 then all is well
>
Silly me - this looks like it was it. While my *installed* version of
freshclam was 0.87, the version that was actually running (which, unlike
previous updates, did not stop and restart upon upgrade) was still 0.86.2.
Simply restarting freshclam gave "normal" messages in my freshclam.log. I
suspect that I'll get fewer of those outdated messages in tomorrow morning's
log message.
Thanks!
-Don
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
