diff options
Diffstat (limited to 'man/nm-online.xml')
| -rw-r--r-- | man/nm-online.xml | 28 |
1 files changed, 7 insertions, 21 deletions
diff --git a/man/nm-online.xml b/man/nm-online.xml index a0db6b3d..87672f74 100644 --- a/man/nm-online.xml +++ b/man/nm-online.xml @@ -59,14 +59,8 @@ <para>This tool is not very useful to call directly. It is however used by <literal>NetworkManager-wait-online.service</literal> with - <literal>--wait-for-startup</literal> argument. This is used to delay - the service and indirectly <literal>network-online.target</literal>, - until networking is up. Don't order your own systemd services after - <literal>NetworkManager-wait-online.service</literal> directly. Instead - if necessary, order your services after <literal>network-online.target</literal>. - Even better is to have your services react to network changes dynamically - and don't order them with respect to <literal>network-online.target</literal> - at all. + <literal>--wait-for-startup</literal> argument + (see <link linkend='NetworkManager-wait-online.service'><citerefentry><refentrytitle>NetworkManager-wait-online.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></link>). </para> <para>By default, connections have the <literal>ipv4.may-fail</literal> and @@ -118,18 +112,8 @@ <command>nm-online -s</command> will just return immediately, regardless of the current network state.</para> <para>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 <literal>connected</literal> - state in NetworkManager. That means, properties like <literal>ipv4.may-fail</literal> and <literal>ipv6.may-fail</literal> - affect whether a certain address family is required. Also, the connection property - <literal>connection.wait-device-timeout</literal> affects whether to wait for - the driver to detect a certain device. Generally, a failure of <literal>NetworkManager-wait-online.service</literal> - 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 <literal>NetworkManager-wait-online.service</literal> - to fail. + For details see + <link linkend='NetworkManager-wait-online.service'><citerefentry><refentrytitle>NetworkManager-wait-online.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></link>. </para> </listitem> </varlistentry> @@ -197,7 +181,9 @@ <refsect1 id='see_also'><title>See Also</title> <para><link linkend='nmcli'><citerefentry><refentrytitle>nmcli</refentrytitle><manvolnum>1</manvolnum></citerefentry></link>, - <link linkend='NetworkManager'><citerefentry><refentrytitle>NetworkManager</refentrytitle><manvolnum>8</manvolnum></citerefentry></link>.</para> + <link linkend='NetworkManager'><citerefentry><refentrytitle>NetworkManager</refentrytitle><manvolnum>8</manvolnum></citerefentry></link>, + <link linkend='NetworkManager-wait-online.service'><citerefentry><refentrytitle>NetworkManager-wait-online.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></link>. + </para> </refsect1> </refentry> |