░▒▓████████████████████████████████▓▒░ ░▒▓█ ▓▒░ ░▒▓█ ~ S W A M P ~ ▓▒░ ░▒▓█ ▓▒░ ░▒▓████████████████████████████████▓▒░
pplmvsvm
LOCATION:
/etc/systemd/system/network-online.target.wants
☗ ROOT
↻ REFRESH
✎ CARVE FLESH
EDITING: NetworkManager-wait-online.service
[Unit] Description=Network Manager Wait Online Documentation=man:NetworkManager-wait-online.service(8) 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=/usr/bin/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
CANCEL
Name
Type
Size
Modified
Actions
↩ ..
DIR
—
—
📄 NetworkManager-wait-online.service
SERVICE
1.1 KB
2025-10-27 19:11
EDIT
📄 systemd-networkd-wait-online.service
SERVICE
785 B
2026-06-05 15:36
EDIT