Bug#391892: exim4-base: combination of logrotate file and cron.d file result in spurious warning mails

[Stephen Gran]

This one time, at band camp, Marc Haber said:
> On Mon, Oct 09, 2006 at 10:56:40AM +0100, Stephen Gran wrote:
> > /etc/logrotate.d/exim4-base contains a size parameter, preventing
> > it from rotating until the paniclog grows to this size.
> > /etc/cron.daily/exim4-base checks the paniclog every day, and by
> > default, sends an email if paniclog is a non-zero size.  This
> > combination results in sending an email every day about the same single
> > issue.  I have finally commented out the check panic log option in the
> > cron.daily script, although I consider this suboptimal - I would prefer
> > that it was just logrotated daily.  I can of course make all the
> > modifications myself, but it seems to me this is a poor default
> > arrangement.  Can the logrotate script go back to daily for the
> > paniclog?
> 
> The idea is that the paniclog is rotated manually after the reason for
> the panicloc entry has been resolved. The paniclog logrotate.d entry
> is only geared to prevent the disk from filling up.

So if there is ever an error that results in a write to paniclog, the
local admin has to move it out of the way manually?  Or am I
misunderstanding you?

Thanks,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran at debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-maintainers/attachments/20061009/0a847c19/attachment.pgp