Your message dated Thu, 12 Oct 2006 11:10:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391892: exim4-base: combination of logrotate file and
cron.d file result in spurious warning mails
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: exim4-base
Version: 4.63-4
Severity: normal
Hello,
/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?
Thanks,
-- Package-specific info:
Exim version 4.63 #1 built 01-Oct-2006 14:40:57
Copyright (c) University of Cambridge 2006
Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dsearch nis
nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
dc_eximconfig_configtype='smarthost'
dc_other_hostnames='gashuffer.lobefin.net'
dc_local_interfaces='127.0.0.1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.lobefin.net'
CFILEMODE='644'
dc_use_split_config='true'
dc_hide_mailname='false'
dc_mailname_in_oh='true'
mailname:gashuffer.lobefin.net
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF8)
Versions of packages exim4-base depends on:
ii adduser 3.97 Add and remove users and groups
ii cron 3.0pl1-97 management of regular background p
ii debconf [debconf-2.0] 1.5.5 Debian configuration management sy
ii exim4-config [exim4-config-2 4.63-4 configuration for the exim MTA (v4
ii libc6 2.3.6.ds1-5 GNU C Library: Shared libraries
ii libdb4.3 4.3.29-6 Berkeley v4.3 Database Libraries [
ii lsb-base 3.1-17 Linux Standard Base 3.1 init scrip
ii netbase 4.27 Basic TCP/IP networking system
Versions of packages exim4-base recommends:
ii psmisc 22.3-1 Utilities that use the proc filesy
-- debconf information:
exim4/purge_spool: false
exim4/move_exim3_spool: false
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [EMAIL PROTECTED] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
This one time, at band camp, Marc Haber said:
> On Tue, Oct 10, 2006 at 01:02:25AM +0100, Stephen Gran wrote:
> > OK, I think that we are just going to have to agree to disagree on
> > this one. I think it violates the principle of least surprise, but you
> > (I understand) think that making sure admins get the message is top
> > priority, even if it means more work for them.
>
> To make this more bearable, I have added a section documenting the
> entire daily cron job to README.Debian in 4.63-5, and have modified
> the init script to issue an alert if a non-empty paniclog is found.
>
> If this makes the situation easier for you, please close the bug
> report. Otherwise, suggest what to do.
That's fine for me, I think. Thanks,
--
-----------------------------------------------------------------
| ,''`. Stephen Gran |
| : :' : [EMAIL PROTECTED] |
| `. `' Debian user, admin, and developer |
| `- http://www.debian.org |
-----------------------------------------------------------------
signature.asc
Description: Digital signature
--- End Message ---
