Your message dated Sat, 16 Sep 2006 20:57:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: logwatch
Version: 7.3-1
Severity: normal
I have some log files in a different directory than /var/log
and a previous version of logwatch responded to --logdir
option and used those files. the only thing in that directory
is appache logs. Now when I run it from the cron job, it uses /var/log even
though --logdir is specified.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages logwatch depends on:
ii perl 5.8.8-4 Larry Wall's Practical Extraction
ii sendmail-bin [mail-transport- 8.13.7-2 powerful, efficient, and scalable
logwatch recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I'm closing this bug, because it's a configuration issue.
Willi
--- End Message ---
