Jonathan Dowland <j...@debian.org> writes:
> On Sun, Sep 21, 2014 at 02:40:31PM +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.
>
> What init system are you using?
the default init system of Wheezy
> If systemd, you might be able to find out by inspecting the log for
> the exim4 service unit, once it has finally started. 'systemd status
> -l exim4.service' is probably one way to do that (my systemd-running
> machine is not presently available for me to confirm, as I'm moving it
> between rooms).
[root@yun:/etc/shorewall]$ systemctl status -l exim.service
exim.service - Exim Mail Transport Agent
Loaded: loaded (/usr/lib/systemd/system/exim.service; enabled)
Active: active (running) since Fri 2014-09-05 19:30:42 CEST; 2 weeks 6 days
ago
Main PID: 970 (exim)
CGroup: /system.slice/exim.service
└─970 /usr/sbin/exim -bd -q1h
Sep 05 19:30:42 yun.yagibdah.de systemd[1]: Started Exim Mail Transport Agent.
[root@yun:/etc/shorewall]$
It works on Fedora, yet it won't tell me anything why it would take long
to start exim and not even how long it takes. So much to the advantages
of systemd ...
BTW, how is systemd supposed to inform me that the MTA is down when it
cannot send me an email to tell me this because the MTA is down? If it
can inform me at all --- can it? So far, it hasn't informed me of
anything at all yet.
--
Knowledge is volatile and fluid. Software is power.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/871tqz1edn....@yun.yagibdah.de
