I'm not entirely sure, but based on the information provided here it
looks like there may have been an override file in place which later got
removed.
If this bug is still occurring and/or reproducible then I'll happily
look into it. However, if it is not longer happening then I suspect this
was
/etc/init.d/exim4 was only modified to make the queue interval 15m instead
of 30m.
What I did next was to execute update-rc.d exim4 default and it seems to
have stopped throwing that error. Strange.
Andreas Metzler [24/01/10 15:58 +0100]:
On 2010-01-12 Suresh Ramasubramanian sur...@hserus.net
On 2010-01-12 Suresh Ramasubramanian sur...@hserus.net wrote:
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy I got
these warnings, and then exim4 did not restart automatically.
/etc/init.d/exim4 start did start
On 2010-01-12 Suresh Ramasubramanian sur...@hserus.net wrote:
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy
[...]
Was this a dist-upgrade from lenny?
cu andreas
--
`What a good friend you are to him, Dr.
On 2010-01-24 Suresh Ramasubramanian sur...@hserus.net wrote:
Andreas Metzler [24/01/10 15:58 +0100]:
[...]
is /etc/init.d/exim4 locally modified, removing the lsb headers?
Either way please add it to the bugreport.
[...]
/etc/init.d/exim4 was only modified to make the queue interval 15m
Andreas Metzler [24/01/10 16:18 +0100]:
Ok. Would you mind sending it to the bts, so we have a complete file
when I re-assign to insserv.
Below. Only change is QUEUEINTERVAL was changed to 15m from the default 30m
srs
#! /bin/sh
# /etc/init.d/exim4
#
# Written by Miquel van
Andreas Metzler [24/01/10 16:11 +0100]:
On 2010-01-12 Suresh Ramasubramanian sur...@hserus.net wrote:
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy
[...]
Was this a dist-upgrade from lenny?
nope. fresh
Hi,
On Sun, Jan 24, 2010 at 07:28:42AM -0800, Suresh Ramasubramanian wrote:
Below. Only change is QUEUEINTERVAL was changed to 15m from the default 30m
I don't have anything to say for the actual problem, but...
#read default file
QUEUERUNNER='combined'
QUEUEINTERVAL='15m'
UPEX4OPTS=''
# Hello,
#
# afaict this is not a exim4 problem. The package's init-script has
# included dependency info since 4.62-3 (July 2006, that is before
# oldstable se bug #376953). The submitter's copy of the init-script
# was not changed substantially. I am therefore reassigning the bug to
# insserv.
Marc Haber [24/01/10 16:36 +0100]:
It is not necessary to modify the init script to override these
settings, just override them from /etc/default/exim4.
Which I did, already once I remembered. Didnt modify the initscript back to
the default though. Both those files say 15m now.
--
To
Hi Suresh,
On Mon, Jan 11, 2010 at 10:01:29PM -0800, Suresh Ramasubramanian wrote:
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy I got these
warnings, and then exim4 did not restart automatically. /etc/init.d/exim4
start
did start it after that.
Setting up exim4-base
* Marc Haber [Tuesday, 12 January 2010 3:58 PM]:
On Mon, Jan 11, 2010 at 10:01:29PM -0800, Suresh Ramasubramanian wrote:
Setting up exim4-base (4.71-3) ...
Installing new version of config file /etc/cron.daily/exim4-base ...
insserv: warning: current start runlevel(s) (empty) of script
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy I got these
warnings, and then exim4 did not restart automatically. /etc/init.d/exim4 start
did start it after that.
Setting up exim4-base (4.71-3) ...
Installing new
13 matches
Mail list logo
