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
The current version of logwatch (6.1.2) picks up freshclam fine, if you want
to rotate freshclam.log try adding someting like this to /etc/logrotate.d
# cat freshclam
/var/log/freshclam.log {
daily
missingok
rotate 30
compress
delaycompress
notifempty
create 600 clamav root
sharedscripts
postrotate
/etc/init.d/freshclamd restart
endscript
}
also have a look in /var/log/messages, which is most likely where clamav is
logging.
you could also set LogVerbose in clamd.conf and freshclam.conf and restart
them both. Have a look at the logs afterwards, that should help you find out
which version you are *really* running, or wether you have got a mixup in
your install, which seems quite common when RPMs are used to install, if that
is how you did it ;-|
Remember to switch off LogVerbose afterwards!
HTH
--
-----------------
Bob Hutchinson
Midwales dot com
-----------------
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
