Quoting matthew stanger :
For 'Type=dbus' services, which most of the distro's use in MM's service
file. Systemd will consider the unit started immediately after the main
service process has been forked off and the service has acquired a name on
the D-Bus bus, as configured by 'BusName='.
I
>
> But how does systemd measure the "boot time" of each? Is it only the
> time needed by the daemon to be exposed in DBus? Or what?
For 'Type=dbus' services, which most of the distro's use in MM's service
file. Systemd will consider the unit started immediately after the main
service process has
> > on my embedded system, "systemd-analyze blame" says:
> >
> > 15.254s ModemManager.service
> > 10.562s NetworkManager.service
> > ...
> >
> > I.e. MM and NM are the two slowest services in terms of start time.
> > Is there anything I can do about it or try
On Wed, 2019-02-13 at 16:01 +0100, W. Martin Borgert wrote:
> Hi,
>
> on my embedded system, "systemd-analyze blame" says:
>
> 15.254s ModemManager.service
> 10.562s NetworkManager.service
> ...
>
> I.e. MM and NM are the two slowest services in terms of
Hi,
on my embedded system, "systemd-analyze blame" says:
15.254s ModemManager.service
10.562s NetworkManager.service
...
I.e. MM and NM are the two slowest services in terms of start time.
Is there anything I can do about it or try to find out, why they
take
