diff options
Diffstat (limited to 'data/NetworkManager-wait-online.service.in')
| -rw-r--r-- | data/NetworkManager-wait-online.service.in | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/data/NetworkManager-wait-online.service.in b/data/NetworkManager-wait-online.service.in index 89632468..26a8f253 100644 --- a/data/NetworkManager-wait-online.service.in +++ b/data/NetworkManager-wait-online.service.in @@ -6,9 +6,27 @@ 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 --timeout=30 +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=30 + [Install] WantedBy=network-online.target |