diff options
Diffstat (limited to 'docs/api/html/NetworkManager-wait-online.service.html')
| -rw-r--r-- | docs/api/html/NetworkManager-wait-online.service.html | 33 |
1 files changed, 28 insertions, 5 deletions
diff --git a/docs/api/html/NetworkManager-wait-online.service.html b/docs/api/html/NetworkManager-wait-online.service.html index 2e252200..76b703a0 100644 --- a/docs/api/html/NetworkManager-wait-online.service.html +++ b/docs/api/html/NetworkManager-wait-online.service.html @@ -8,7 +8,7 @@ <link rel="up" href="manpages.html" title="Part I. Manual Pages"> <link rel="prev" href="NetworkManager-dispatcher.html" title="NetworkManager-dispatcher"> <link rel="next" href="nmcli.html" title="nmcli"> -<meta name="generator" content="GTK-Doc V1.33.0 (XML mode)"> +<meta name="generator" content="GTK-Doc V1.33.1 (XML mode)"> <link rel="stylesheet" href="style.css" type="text/css"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> @@ -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 @@ -105,9 +114,23 @@ 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 @@ -145,6 +168,6 @@ </div> </div> <div class="footer"> -<hr>Generated by GTK-Doc V1.33.0</div> +<hr>Generated by GTK-Doc V1.33.1</div> </body> </html> \ No newline at end of file |