From 9959fdb2e8ddd06f2161798ca0a39c77d67c652d Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 4 May 2022 15:35:24 +0200 Subject: New upstream version 1.37.92 --- docs/api/html/nm-online.html | 32 +++++++++----------------------- 1 file changed, 9 insertions(+), 23 deletions(-) (limited to 'docs/api/html/nm-online.html') diff --git a/docs/api/html/nm-online.html b/docs/api/html/nm-online.html index 84fef32f..53c2cc52 100644 --- a/docs/api/html/nm-online.html +++ b/docs/api/html/nm-online.html @@ -8,7 +8,7 @@ - + @@ -41,14 +41,8 @@ should be checked (see the return codes below).

This tool is not very useful to call directly. It is however used by NetworkManager-wait-online.service with - --wait-for-startup argument. This is used to delay - the service and indirectly network-online.target, - until networking is up. Don't order your own systemd services after - NetworkManager-wait-online.service directly. Instead - if necessary, order your services after network-online.target. - Even better is to have your services react to network changes dynamically - and don't order them with respect to network-online.target - at all. + --wait-for-startup argument + (see NetworkManager-wait-online.service(8)).

By default, connections have the ipv4.may-fail and ipv6.may-fail properties set to yes; @@ -86,18 +80,8 @@ nm-online -s will just return immediately, regardless of the current network state.

There are various ways to affect when startup complete is reached. - For example, by setting a connection profile to autoconnect, such a profile - possibly will activate during startup and thus delay startup complete being reached. - Also, a profile is considered ready when it fully reached the logical connected - state in NetworkManager. That means, properties like ipv4.may-fail and ipv6.may-fail - affect whether a certain address family is required. Also, the connection property - connection.wait-device-timeout affects whether to wait for - the driver to detect a certain device. Generally, a failure of NetworkManager-wait-online.service - indicates a configuration error, where NetworkManager won't be able to reach the - desired connectivity state during startup. An example for that are bridge or bond master - profiles, that get autoconnected but without activating any slaves. Such master devices - hang in activating state indefinitely, and cause NetworkManager-wait-online.service - to fail. + For details see + NetworkManager-wait-online.service(8).

@@ -145,10 +129,12 @@

See Also