Bug#391892: Suggestion for the warning-mail

Andreas Beck becka-6Kfmt at bedatec.de
Sat May 12 11:24:52 UTC 2007


I have just ran into the same problem Stephen described and would like
to suggest a simple way to solve the problem:

I agree that admins tend to be lazy, so the warning should be repeated
until resolved manually. However the mail about the non-empty paniclog
contains no indication that manually emptying the paniclog is required
or how to do that.

So I suggest to add

"after resolving the error cause, please rotate away the paniclog by
  e.g. using 'logrotate -f /etc/logrotate.d/exim4-base'."

to the mail message or some similar hint.

This avoids the confusion of "What? Still an error? I fixed that
yesterday, didn't I?".


Background:
I also had a config error that in previous versions only yielded a
warning and fixed it with the first mail about it. Next day, same
warning. I looked and found nothing new, so I left it at it, assuming
the paniclog file would rotate away now. A few days later I still get
the mails and think "hmm - rotates weekly?". After some more days I get
annoyed and check to see it rotates on size. I was tempted to pull it to
weekly, but then first checked if the problem was known and the
discussion here convinced me that it is correct to require manual
interaction, but think one should be told explicitly that it is
required.

CU, ANdy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4715 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-maintainers/attachments/20070512/f2e00ff1/smime.bin


More information about the Pkg-exim4-maintainers mailing list