Your message dated Mon, 30 Apr 2012 08:07:32 +0200
with message-id <[email protected]>
has caused the report #670877,
regarding logwatch: the parameter --logdir is partially ignored
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
670877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670877
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Hi!
I got attached bug report via the Debian bug tracking system. IMHO,
logwatch should really change behaviour here, particularly as the change
would be quite easy,
WM
-------- Original Message --------
Subject: Bug#670877: logwatch: the parameter --logdir is partially ignored
Resent-Date: Sun, 29 Apr 2012 21:33:02 +0000
Resent-From: Maarten Derickx <[email protected]>
Resent-To: [email protected]
Resent-CC: Willi Mann <[email protected]>
Date: Sun, 29 Apr 2012 23:25:03 +0200
From: Maarten Derickx <[email protected]>
Reply-To: Maarten Derickx <[email protected]>,
[email protected]
To: Debian Bug Tracking System <[email protected]>
Package: logwatch
Version: 7.3.6.cvs20090906-1squeeze1
Severity: minor
I copied some logfiles to /tmp because I only wanted to know what was in
those files and When I did
logwatch --logdir /tmp
I also got a lot of logwatch output related to for example apache while
there where no apache logs in /tmp. It seems like it also goes to
/var/log for files it cannot find in /tmp wich again doesn't mach the
documentation.
--logdir directory
Look in directory for log subdirectories or log files
instead of the default directory.
It clearly sais instead and not in adition to or something like "first
look in directory and if not is found look in the default directory".
So I hope either the documentation or the behaviour can get changed.
Documentation is probably easier but behaviour would be more usefull.
Thanks Maarten
-- System Information:
Debian Release: 6.0.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (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/dash
Versions of packages logwatch depends on:
ii exim4 4.72-6+squeeze2 metapackage to ease Exim
MTA (v4)
ii exim4-daemon-light [ma 4.72-6+squeeze2 lightweight Exim MTA (v4)
daemon
ii perl 5.10.1-17squeeze3 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 [Errno 2] No such file or directory:
u'/etc/cron.daily/00logwatch'
-- no debconf information
--- End Message ---
