From 0018d1f3cf71d680d7b6bceda55a5717244d8b26 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Tue, 16 Aug 2022 18:24:19 +0200
Subject: New upstream version 1.39.90

---
 .../html/NetworkManager-wait-online.service.html   | 29 +++++++++++++++++++---
 1 file changed, 26 insertions(+), 3 deletions(-)

(limited to 'docs/api/html/NetworkManager-wait-online.service.html')

diff --git a/docs/api/html/NetworkManager-wait-online.service.html b/docs/api/html/NetworkManager-wait-online.service.html
index 3f6d63d1..76b703a0 100644
--- a/docs/api/html/NetworkManager-wait-online.service.html
+++ b/docs/api/html/NetworkManager-wait-online.service.html
@@ -75,7 +75,8 @@
       and how long <code class="literal">NetworkManager-wait-online.service</code> blocks.
       </p>
 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p>
+<li class="listitem">
+<p>
             In general, startup complete is not reached as long as NetworkManager is busy
             activating a device and as long as there are profiles in activating state.
             During boot, NetworkManager starts autoactivating
@@ -84,7 +85,15 @@
             setting). While trying and retrying, NetworkManager is busy until all
             profiles and devices either reached an activated or disconnected state
             and no further events are expected.
-          </p></li>
+          </p>
+<p>
+          </p>
+<p>
+            Basically, as long as there are devices and connections in <code class="literal">activating</code>
+            state visible with <span class="command"><strong>nmcli device</strong></span> and <span class="command"><strong>nmcli connection</strong></span>,
+            startup is still pending.
+          </p>
+</li>
 <li class="listitem"><p>
             When a device reaches activated state, depends on its configuration.
             For example, with a profile with both IPv4 and IPv6 addressing
@@ -104,10 +113,24 @@
             without ports, <code class="literal">NetworkManager-wait-online.service</code> blocks until timeout.
             This is a configuration error.
           </p></li>
+<li class="listitem"><p>
+            Dispatcher scripts for the "pre-up" event run at a late stage during activation
+            of a profile. These scripts block the activation for when NetworkManager considers
+            the profile fully activated.
+            See also <a class="link" href="NetworkManager-dispatcher.html" title="NetworkManager-dispatcher"><span class="citerefentry"><span class="refentrytitle">NetworkManager-dispatcher</span>(8)</span></a>
+            for details.
+          </p></li>
+<li class="listitem"><p>
+            The connection property <code class="literal">connection.wait-activation-delay</code> also
+            adds an additional delay during activation and delays startup complete. This is to
+            workaround certain cases where a device is known to not be ready for a certain
+            amount of time.
+          </p></li>
 <li class="listitem"><p>
             The property <code class="literal">connection.wait-device-timeout</code> of the connection
             profiles waits until the waited devices appear. This is useful if the driver
-            takes a longer time to detect the networking interfaces.
+            takes a longer time to detect the networking interfaces. Similar with the
+            <code class="literal">connection.gateway-ping-timeout</code> property.
           </p></li>
 <li class="listitem"><p>
             With Wi-Fi devices, NetworkManager needs to wait for the first scan
-- 
cgit 1.3.0-6-gf8a5