On Sat, 2015-01-24 at 00:42 +0100, Paul Menzel wrote:
Dear Thomas, thank you for your reply! Am Freitag, den 23.01.2015, 11:42 +0100 schrieb Thomas Haller:On Fri, 2015-01-23 at 08:37 +0100, Paul Menzel wrote:Running `systemd-analyze blame`, it shows that the service NetworkManager still needs 580 ms to finish. Note that this is smaller than the actual needed time.I think that systemd declares NetworkManager as started after NM acquires its DBUS interface. What do you mean with "the actual needed time"?Thank you for clearing that up. I mean that this does not mean that the interfaces have actually been configured and the network is usable.
Hi, "network usable" might be significantly later, and your services usually should not wait for such an event. See http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ You would also not sort services that require NetworkManagers DBUS API "After=NetworkManager". Hence they wouldn't have to wait full 580ms but instead start in parallel and block until NetworkManager being ready to answer requests on DBUS. So neither of this ~should~ delay your boot, but checking with systemd-analyze might be interesting. Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part