Policy on cron.* scripts (was: Re: Still exim problem)
- To: debian-policy@lists.debian.org
- Subject: Policy on cron.* scripts (was: Re: Still exim problem)
- From: Arthur Korn <arthur@korn.ch>
- Date: Fri, 6 Oct 2000 10:43:09 +0200
- Message-id: <20001006104309.A8654@korn.ch>
- Mail-followup-to: debian-policy@lists.debian.org
- In-reply-to: <20001006100914.A14476@compusol.com.au>; from bod@compusol.com.au on Fri, Oct 06, 2000 at 10:09:14AM +1100
- References: <20001005002352.A25243@aziraphale.demon.co.uk> <39DC2162.DE8A4FCA@seabone.net> <20001006100914.A14476@compusol.com.au>
Hi
Brendan O'Dea schrieb:
> On Thu, Oct 05, 2000 at 08:36:18AM +0200, Fabio Massimo Di Nitto wrote:
> >[...]it's still reporting me each cron.daily
> >execution this
> >message:
> >
> >/etc/cron.daily/exim:
> >Exim retry database in spool /var/spool/exim
>
> This message appears to be produced unconditionally by exim_tidydb (see
> exim_tidydb.c, line 162).
>
> The program should probably be changed to be less verbose, or to output
> error messages on stderr so that the crontab entry may redirect stdout
> to /dev/null.
Probably it should be clearly stated in policy that the cron.*
scripts may be quiet if no errors are encountered.
Running logcheck can be really amusing sometimes ... ;)
ciao, 2ri
--
"I heard if you play the NT-CD backwards, you get a satanic message."
"That's nothing, if you play it forward, it installs NT"
Reply to: