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

Packit Service b23acc
[Unit]
Packit Service b23acc
Description=Network Manager Wait Online
Packit Service b23acc
Documentation=man:nm-online(1)
Packit Service b23acc
Requires=NetworkManager.service
Packit Service b23acc
After=NetworkManager.service
Packit Service b23acc
Before=network-online.target
Packit Service b23acc
Packit Service b23acc
[Service]
Packit Service b23acc
# `nm-online -s` waits until the point when NetworkManager logs
Packit Service b23acc
# "startup complete". That is when startup actions are settled and
Packit Service b23acc
# devices and profiles reached a conclusive activated or deactivated
Packit Service b23acc
# state. It depends on which profiles are configured to autoconnect and
Packit Service b23acc
# also depends on profile settings like ipv4.may-fail/ipv6.may-fail,
Packit Service b23acc
# which affect when a profile is considered fully activated.
Packit Service b23acc
# Check NetworkManager logs to find out why wait-online takes a certain
Packit Service b23acc
# time.
Packit Service b23acc
Packit Service b23acc
Type=oneshot
Packit Service b23acc
ExecStart=@bindir@/nm-online -s -q
Packit Service b23acc
RemainAfterExit=yes
Packit Service b23acc
Packit Service b23acc
# Set $NM_ONLINE_TIMEOUT variable for timeout in seconds.
Packit Service b23acc
# Edit with `systemctl edit NetworkManager-wait-online`.
Packit Service b23acc
#
Packit Service b23acc
# Note, this timeout should commonly not be reached. If your boot
Packit Service b23acc
# gets delayed too long, then the solution is usually not to decrease
Packit Service b23acc
# the timeout, but to fix your setup so that the connected state
Packit Service b23acc
# gets reached earlier.
Packit Service b23acc
Environment=NM_ONLINE_TIMEOUT=30
Packit Service b23acc
Packit Service b23acc
[Install]
Packit Service b23acc
WantedBy=network-online.target