|
Nope.
the problem is that systemd assumes the network is ready for use as soon as it starts NetworkManager.
When this is the case, nearly all network dependent actions fail - from network based filesystems, name lookups, time synchronization, databases, network user identifications (LDAP/NIS/...).
So much fails that the systemd developers had to start modifying a ton of other applications (this one being NetworkManager).
NetworkManager-wait-online is required to delay until the network is usable. This required modification of NetworkManager to explicitly send a "ready" signal back to systemd. This normally works (DHCP clients got modified too). And even the database servers got modified for the same reason.
This is one of the reasons systemd is considered a poor design, and imposes a LOT of things on services.
|
