Package: logwatch
Version: 7.3.6.cvs20090906-1
Severity: normal
Tags: squeeze lenny

This bug affects Lenny and Squeeze, and is present as of Lenny, due to switching
from sysklogd to rsyslog (source: http://wiki.debian.org/Rsyslog). This update
causes rotated log files to be suffixed with a .1 instead of .0.

The same bug was reported at Launchpad for Ubuntu 10.04 Lucid, see
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/606715

Some logfile definitions in /usr/share/logwatch/{default,dist}.conf should be 
updated
to reflect these changes to syslog:
/usr/share/logwatch/default.conf/logfiles$ grep -e 'LogFile.*\.0' *
kernel.conf:LogFile = kern.log.0
daemon.conf:LogFile = daemon.log.0
maillog.conf:LogFile = mail.log.0
syslog.conf:LogFile = syslog.0
secure.conf:LogFile = auth.log.0

/usr/share/logwatch/dist.conf/logfiles$ grep -e 'LogFile.*\.0' *
maillog.conf:LogFile = mail.log.0
messages.conf:LogFile = messages.0

This bug could lead to missing information in logwatch reports.

Thanks

-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.36 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages logwatch depends on:
ii  exim4                         4.72-6     metapackage to ease Exim MTA (v4) 
ii  exim4-daemon-heavy [mail-tran 4.72-6     Exim MTA (v4) daemon with extended
ii  perl                          5.10.1-17  Larry Wall's Practical Extraction 

Versions of packages logwatch recommends:
ii  libdate-manip-perl            6.11-1     module for manipulating dates

Versions of packages logwatch suggests:
pn  fortune-mod                   <none>     (no description available)

-- Configuration Files:
/etc/cron.daily/00logwatch changed:
test -x /usr/share/logwatch/scripts/logwatch.pl || exit 0
/usr/sbin/logwatch --mailto [email protected]


-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to