mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-07-21 10:14:41 +00:00
f59f1a25b4
> If there is no network [1] to connect to (if network interface is down [2]) > NetworkManager will make "nm-online -s" stop [3] without waiting. [1] we usually talk about connection profiles or devices/interfaces [2] it would be better to say, if no suitable profile is ready to autoconnect. [3] `nm-online -s` waits until NetworkManager declares "startup complete" reached. I find the wording of the comment not very clear or useful. Possibly I don't understand it properly, but that is a problem for a comment that is supposed to help. Remove it.
33 lines
1.1 KiB
SYSTEMD
33 lines
1.1 KiB
SYSTEMD
[Unit]
|
|
Description=Network Manager Wait Online
|
|
Documentation=man:nm-online(1)
|
|
Requires=NetworkManager.service
|
|
After=NetworkManager.service
|
|
Before=network-online.target
|
|
|
|
[Service]
|
|
# `nm-online -s` waits until the point when NetworkManager logs
|
|
# "startup complete". That is when startup actions are settled and
|
|
# devices and profiles reached a conclusive activated or deactivated
|
|
# state. It depends on which profiles are configured to autoconnect and
|
|
# also depends on profile settings like ipv4.may-fail/ipv6.may-fail,
|
|
# which affect when a profile is considered fully activated.
|
|
# Check NetworkManager logs to find out why wait-online takes a certain
|
|
# time.
|
|
|
|
Type=oneshot
|
|
ExecStart=@bindir@/nm-online -s -q
|
|
RemainAfterExit=yes
|
|
|
|
# Set $NM_ONLINE_TIMEOUT variable for timeout in seconds.
|
|
# Edit with `systemctl edit NetworkManager-wait-online`.
|
|
#
|
|
# Note, this timeout should commonly not be reached. If your boot
|
|
# gets delayed too long, then the solution is usually not to decrease
|
|
# the timeout, but to fix your setup so that the connected state
|
|
# gets reached earlier.
|
|
Environment=NM_ONLINE_TIMEOUT=60
|
|
|
|
[Install]
|
|
WantedBy=network-online.target
|