2011-04-06 04:30:02 +02:00
|
|
|
[Unit]
|
|
|
|
|
Description=Network Manager Wait Online
|
2016-06-02 17:41:29 +02:00
|
|
|
Documentation=man:nm-online(1)
|
2017-11-02 15:14:18 +01:00
|
|
|
Requires=NetworkManager.service
|
2011-05-10 16:34:11 -05:00
|
|
|
After=NetworkManager.service
|
2015-03-11 16:28:34 +01:00
|
|
|
Before=network-online.target
|
2011-04-06 04:30:02 +02:00
|
|
|
|
|
|
|
|
[Service]
|
2020-04-28 22:12:21 +02:00
|
|
|
# `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.
|
|
|
|
|
|
2011-04-06 04:30:02 +02:00
|
|
|
Type=oneshot
|
2020-04-28 22:12:21 +02:00
|
|
|
ExecStart=@bindir@/nm-online -s -q
|
2016-06-02 17:58:35 +02:00
|
|
|
RemainAfterExit=yes
|
2011-04-06 04:30:02 +02:00
|
|
|
|
2020-04-28 22:12:21 +02:00
|
|
|
# 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=30
|
|
|
|
|
|
2011-04-06 04:30:02 +02:00
|
|
|
[Install]
|
2015-03-11 16:25:54 +01:00
|
|
|
WantedBy=network-online.target
|
