File NetworkManager-make-nm-wait-online-follow-nm-service.patch of Package NetworkManager.11070
From 167e42a87e97ed7fb26a4263c22f1774716ac51b Mon Sep 17 00:00:00 2001
From: Alan Jenkins <firstname.lastname@example.org>
Date: Sun, 11 Mar 2018 21:48:46 +0000
Subject: [PATCH] systemd: make enablement of n-m-wait-online.service follow
This is the approach used by systemd-networkd.
I don't understand the logic that caused systemd-networkd to make the change -
Instead, I am suggesting it for consistency, and because it seems to me this is the
exact correct behaviour. Because if you enable NetworkManager, and rely on it to
configure your network devices, then network mounts will not start correctly at boot
time unless you also enable NetworkManager-wait-online.service.
Enabling NetworkManager-wait-online.service does not cause unnecessary serialization
of the boot process; it is only pulled in if something else (like a network mount)
pulls in network-online.target.
I am suggesting this in response to reading this user support request .
[email@example.com: reworded commit message]
data/NetworkManager.service.in | 5 +++++
1 file changed, 5 insertions(+)
@@ -27,3 +27,8 @@ WantedBy=multi-user.target
+# We want to enable NetworkManager-wait-online.service whenever this service
+# is enabled. NetworkManager-wait-online.service has
+# WantedBy=network-online.target, so enabling it only has an effect if
+# network-online.target itself is enabled or pulled in by some other unit.