Package: logtail
Version: 1.2.61
Severity: important

Recently logcheck stopped working on my system and after running it
manually I traced it to logtail2... I'd recently been forced to delete
the archived logs on my system in order to make some space and that
appears to confuse logtail2 completely...

e.g.:
[EMAIL PROTECTED]:~# logtail2 -t /var/log/syslog
Cannot get /var/log/syslog.1.gz mtime: No such file or directory

If I create that file it then works fine.
I'm not sure why it needs to have that file existing in the first place
and surely this will break new systems which haven't rotated any logs
yet?

-- System Information:
Debian Release: lenny/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), 
(500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-k7 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages logtail depends on:
ii  perl                          5.8.8-7    Larry Wall's Practical Extraction 

logtail recommends no packages.

-- no debconf information



_______________________________________________
Logcheck-devel mailing list
Logcheck-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/logcheck-devel

Reply via email to