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