From 02a31e71afbc1f62dfead8eb08878d10b1efaf95 Mon Sep 17 00:00:00 2001 From: Beniamino Galvani Date: Thu, 23 Apr 2020 17:24:22 +0200 Subject: [PATCH] man: mention the meaning of may-fail in the nm-online man page Commit b2a0738765d3 ('man: improve manual page for nm-online') removed the explanation of how may-fail can be used to wait for a specific address family during boot. I found that part useful. Add it again, adapting it to the new behavior introduced by 1e5206414af8 ('device: don't delay startup complete for pending-actions "autoconf", "dhcp4" and "dhcp6"'). https://bugzilla.redhat.com/show_bug.cgi?id=1825666 (cherry picked from commit 25583de20ba0df49d9364c580011d4c75c3be8f8) --- man/nm-online.xml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/man/nm-online.xml b/man/nm-online.xml index 87072ec3b8..c36dda8dd8 100644 --- a/man/nm-online.xml +++ b/man/nm-online.xml @@ -68,6 +68,14 @@ and don't order them with respect to network-online.target at all. + + By default, connections have the ipv4.may-fail and + ipv6.may-fail properties set to yes; + this means that NetworkManager waits for one of the two address families to + complete configuration before considering the connection activated. If you + need a specific address family configured before + network-online.target is reached, set the corresponding + may-fail property to no. Options