NetworkManager/data/NetworkManager-wait-online.service.in

[Unit]
Description=Network Manager Wait Online
Documentation=man:nm-online(1)
Requires=NetworkManager.service
After=NetworkManager.service
Before=network-online.target

[Service]
Type=oneshot
ExecStart=@bindir@/nm-online -s -q --timeout=30
RemainAfterExit=yes

[Install]
WantedBy=network-online.target
systemd: pull in network.service and introduce NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008 2011-04-06 02:30:02 +00:00			`[Unit]`
			`Description=Network Manager Wait Online`
systemd: add Documentation to service files Reference the nm-online and NetworkManager man page in the corresponding service files. https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Documentation= https://bugzilla.gnome.org/show_bug.cgi?id=767168 2016-06-02 15:41:29 +00:00			`Documentation=man:nm-online(1)`
systemd: let "NetworkManager-wait-online.service" require "NetworkManager.service" `systemctl start network-online.target` should suffice to start "NetworkManager.service". That would work because - "network-online.target" has "Wants=NetworkManager-wait-online.service" - "NetworkManager-wait-online.service" has "Require=NetworkManager.service". But previously, "NetworkManager-wait-online.service" would just fail with missing dependency. See also https://github.com/systemd/systemd/pull/6065 which does the same for networkd's wait-online serice, and see rh#1452866 for a use-case. Related: https://bugzilla.redhat.com/show_bug.cgi?id=1452866 2017-11-02 14:14:18 +00:00			`Requires=NetworkManager.service`
systemd: tweak NM-wait-online.service 1) Don't require NM, but run after it. This allows this service to be installed without bringing up NetworkManager. Add -x so that it exits if NM isn't running. 2) Install as a want of network.target, instead of multi-user.target. This allows us to skip it if nothing requires network.target or the legacy $network SysV capability. 2011-05-10 21:34:11 +00:00			`After=NetworkManager.service`
systemd: stop blocking network.target in NetworkManager-wait-online.service network.target is a very early boot target which basically says "I can start opening sockets now". It has nothing to do with being connected to the internet and is often required by early boot services as well. Drop the unnecessary and wrong Wants=/Before=network.target to avoid dependency cycles and boot delays. https://bugzilla.gnome.org/show_bug.cgi?id=746039 https://launchpad.net/1430280 2015-03-11 15:28:34 +00:00			`Before=network-online.target`
systemd: pull in network.service and introduce NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008 2011-04-06 02:30:02 +00:00
			`[Service]`
			`Type=oneshot`
systemd: update NetworkManager-wait-online.service to wait for startup 2014-03-26 17:14:04 +00:00			`ExecStart=@bindir@/nm-online -s -q --timeout=30`
systemd: use RemainAfterExit=yes for NetworkManager-wait-online.service RemainAfterExit=yes is typically used for Type=oneshot services. systemd-networkd-wait-online.service uses it, so we should as well. See https://www.freedesktop.org/software/systemd/man/systemd.service.html#RemainAfterExit= https://www.freedesktop.org/software/systemd/man/systemd.service.html#Type= https://bugzilla.gnome.org/show_bug.cgi?id=767170 2016-06-02 15:58:35 +00:00			`RemainAfterExit=yes`
systemd: pull in network.service and introduce NetworkManager-wait-online.service This pulls in network.target from NetworkManager.service (and not the other way round), as suggested and agreed on on the systemd ML: http://lists.freedesktop.org/archives/systemd-devel/2011-March/001692.html This also introduces an auxiliary service NetworkManager-wait-online.service that can be used to order a unit after the point where the network is available. When this is enabled with "systemd enable NetworkManager-wait-online.service" the unit network.target will be delayed until the network is up, which is suitable for synchronizing NFS mounts and similar to it. https://bugzilla.redhat.com/show_bug.cgi?id=692008 2011-04-06 02:30:02 +00:00
			`[Install]`
systemd: install NetworkManager-wait-online.service into network-online.target This unit "implements" network-online.target, which is fairly independent from multi-user.target, so specify the correct install target. https://bugzilla.gnome.org/show_bug.cgi?id=746039 https://launchpad.net/1430280 2015-03-11 15:25:54 +00:00			`WantedBy=network-online.target`