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

[Unit]
Description=Network Manager Wait Online
Requisite=NetworkManager.service
After=NetworkManager.service
Wants=network.target
Before=network.target network-online.target

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

[Install]
WantedBy=multi-user.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 04:30:02 +02:00			`[Unit]`
			`Description=Network Manager Wait Online`
systemd: fix NetworkManager-wait-online.service to wait for link up (rh #710502) Since commit 0ce4b6b4128f19177072d1bb5f5c3a87783256ba NetworkManager-wait-online.service quits immediately if there is no link yet. Fix it by removing the '-x' option. But if we do just that, NM-w-o would add a useless 30 seconds delay in the case when NM is not running at all. Solve this by adding a Requisite= dependency on NM. https://bugzilla.redhat.com/show_bug.cgi?id=710502 2011-06-17 09:14:23 +02:00			`Requisite=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 16:34:11 -05:00			`After=NetworkManager.service`
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 04:30:02 +02:00			`Wants=network.target`
systemd: update for network-online.target for systemd >= 200 (rh #787314) systemd's new network-online target abstracts the "wait until networking is up" stuff, and NM-wait-online implements that functionality. Thus NM-wait-online should be ordered before (and thus be a dependency of) network-online. 2013-05-15 07:37:25 -05:00			`Before=network.target 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 04:30:02 +02:00
			`[Service]`
			`Type=oneshot`
systemd: fix NetworkManager-wait-online.service to wait for link up (rh #710502) Since commit 0ce4b6b4128f19177072d1bb5f5c3a87783256ba NetworkManager-wait-online.service quits immediately if there is no link yet. Fix it by removing the '-x' option. But if we do just that, NM-w-o would add a useless 30 seconds delay in the case when NM is not running at all. Solve this by adding a Requisite= dependency on NM. https://bugzilla.redhat.com/show_bug.cgi?id=710502 2011-06-17 09:14:23 +02:00			`ExecStart=@bindir@/nm-online -q --timeout=30`
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 04:30:02 +02:00
			`[Install]`
systemd: update for network-online.target for systemd >= 200 (rh #787314) systemd's new network-online target abstracts the "wait until networking is up" stuff, and NM-wait-online implements that functionality. Thus NM-wait-online should be ordered before (and thus be a dependency of) network-online. 2013-05-15 07:37:25 -05:00			`WantedBy=multi-user.target`