|
Server IP : 103.191.208.227 / Your IP : 3.137.175.166 Web Server : LiteSpeed System : Linux emphasis.herosite.pro 4.18.0-553.8.1.lve.el8.x86_64 #1 SMP Thu Jul 4 16:24:39 UTC 2024 x86_64 User : mhmsfzcs ( 1485) PHP Version : 8.1.31 Disable Function : show_source, system, shell_exec, passthru, exec MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON Directory (0755) : /lib/python2.7/../systemd/boot/../system/ |
| [ Home ] | [ C0mmand ] | [ Upload File ] |
|---|
[Unit] Description=Network Manager Wait Online Documentation=man:nm-online(1) 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