logwatch error

Charles Howse chowse at charter.net
Wed Jun 23 15:59:41 UTC 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 23 June 2004 10:45 am, Alexander Dalloz wrote:
> Am Mi, den 23.06.2004 schrieb Charles Howse um 17:17:
> > > > > /etc/cron.daily/00-logwatch:
> > > > >
> > > > > Use of uninitialized value in -x at /etc/cron.daily/00-logwatch
> > > > > line 478. *** Error: There is no logfile defined. Do you have
> > > > > a /etc/log.d/conf/logfiles/freshclam.log.conf file ?
> > > > > - ---------------------------------------
> > > > > The answer to the question is: NO, I don't have
> > > > > a /etc/log.d/conf/logfiles/freshclam.log.conf file.
> >
> > The config file for freshclam lives at /etc/freshclam.conf, and the
> > following files are present:
> > /etc/log.d/conf/logfiles/clam-update.conf
> > /etc/log.d/conf/services/clam-update.conf
> > /etc/log.d/scripts/services/clam-update
> > /etc/log.d/scripts/services/clamav-milter
> > /etc/log.d/scripts/services/clamav
> >
> > Now, what exactly is missing?
> >
> > Charles Howse
>
> Did you run a
>
> find /etc/log.d/ -name "*clam*"
>
> to find all files with "clam" in the name inside the log.d directory?
> From the error message you posted I would expect that there is a
> "/etc/log.d/scripts/services/freshclam" or a
> "/etc/log.d/conf/services/freshclam" file but none in the conf
> directory.

[charles at moe charles]$ find /etc/log.d/ -name "*clam*"
/etc/log.d/conf/logfiles/clam-update.conf
/etc/log.d/conf/services/clam-update.conf
/etc/log.d/conf/services/clamav-milter.conf
/etc/log.d/conf/services/clamav.conf
/etc/log.d/scripts/services/clam-update
/etc/log.d/scripts/services/clamav-milter
/etc/log.d/scripts/services/clamav

[charles at moe charles]$ locate freshclam
/var/log/clamav/freshclam.log
/etc/cron.daily/freshclam
/etc/logrotate.d/freshclam
/etc/freshclam.conf
/usr/share/doc/clamav-0.73/freshclam.conf
/usr/share/man/man1/freshclam.1.gz
/usr/share/man/man5/freshclam.conf.5.gz
/usr/bin/freshclam

Could logwatch be looking for 'freshclam', while the conf files are called 
'clam-update'?

FWIW, logwatch is working with the exception of the error I mentioned.

 ################### LogWatch 5.2 (06/21/04) #################### 
       Processing Initiated: Wed Jun 23 04:02:09 2004
       Date Range Processed: yesterday
     Detail Level of Output: 0
          Logfiles for Host: moe
 ################################################################ 

 --------------------- Clamav Begin ------------------------ 

Daemon check list:
   Database modification detected. Forcing reload: 1 Time(s)

Virus database reloads:
   Now protecting against 22051 viruses: 1 Time(s)

 ---------------------- Clamav End ------------------------- 
[more snipped]

- -- 
Charles Howse
Jackson, TN
Registered Linux User # 347576 (http://counter.li.org)
GnuPG ID - 1F5130A8
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFA2ajt/S+VsB9RMKgRAp8DAJsF9pnDAsc3W/POOmX022rbmMDokwCfdrVF
zG77M/MScKYO7qIgQbn2Ztc=
=YktE
-----END PGP SIGNATURE-----





More information about the users mailing list