On 9/29/05, Don Levey <[EMAIL PROTECTED]> 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?
>  -Don

Yes. I have updated to logwatch-6.1 today.. I am going to see if they
have fixed it or not upstream.



--
Stephen J Smoogen.
CSIRT/Linux System Administrator
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

Reply via email to