Your message dated Sun, 26 Nov 2006 14:51:50 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398836: logwatch documentation should say how its running
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: 5.2.2-5
Severity: minor
When you install logwatch, from reading the man page or README.Debian, you
have no idea how to get logwatch going. It would be useful if
README.Debian said something like 'by default logwatch sets itself up
using cron to automatically run once a day'.
--- End Message ---
--- Begin Message ---
[EMAIL PROTECTED] schrieb:
> Package: logwatch
> Version: 5.2.2-5
> Severity: minor
>
> When you install logwatch, from reading the man page or README.Debian, you
> have no idea how to get logwatch going. It would be useful if
> README.Debian said something like 'by default logwatch sets itself up
> using cron to automatically run once a day'.
$ grep-available -FPackage logwatch -s Description | grep every
Logwatch is a modular log analyser that runs every night
I think that's enough justification to close this bug. Additionally you
can run
$ dpkg -L logwatch
and will see the cron job too.
Willi
--- End Message ---
