Re: starting exim4 takes ages

[lee <lee@yun.yagibdah.de>]

Brian <ad44@cityscape.co.uk> writes:

> On Sun 21 Sep 2014 at 21:01:17 +0200, lee wrote:
>
>> Brian <ad44@cityscape.co.uk> writes:
>> 
>> > On Sun 21 Sep 2014 at 14:40:31 +0200, lee wrote:
>> >
>> >> what might be the reason for exim4 taking ages (i. e. minutes) to start
>> >> when booting?  The boot process keeps waiting until exim has started.
>> >> 
>> >> Exim has been configured with 'dpkg-reconfigure exim4-config'.
>> >
>> > What is dc_minimaldns in /etc/exim4/update-exim4.conf.conf?
>> 
>> dc_minimaldns='false'
>
> This is sensible.
>
> Would you please quantify the time waiting for exim to start more
> precisely? You get the same delay with 'service exim4 restart'?

Restarting exim takes about 2 seconds.  Stopping and starting is
considerably faster.

It takes 20 seconds to start exim when booting.  The problem is with
something starting after exim, probably chronyd.

I had to put a 'sleep' into /etc/init.d/chrony because without it,
chrony goes into offline mode.  Without the sleep, there isn't so much
waiting time, but I have to restart chrony manually.


This is some feature of chrony.  How do I prevent chrony from going into
offline mode without a 'sleep'?  The time server is the dom0 of the VM
chrony runs in, so the server is even /guaranteed/ to be available.


And the NFS volume still isn't mounted automatically and sometimes gets
unexpectedly unmounted for no apparent reason ...


-- 
Knowledge is volatile and fluid.  Software is power.