From: Alvin Šipraga <alsi@bang-olufsen.dk>
Date: Tue, 6 Apr 2021 13:56:05 +0000 (+0200)
Subject: man: clarify RequiredForOnline= behaviour for online state
X-Git-Tag: v249-rc1~204^2~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6c95e09388a527ec053efb631f93188458dd95e6;p=thirdparty%2Fsystemd.git

man: clarify RequiredForOnline= behaviour for online state

With new "online state" semantics in networkd, make the description of
RequiredForOnline= a little more broad.
---

diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index 02e464b193d..d1c823789ff 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -215,9 +215,9 @@
           <para>Takes a boolean or a minimum operational state and an optional maximum operational state.
           Please see <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
           for possible operational states. When <literal>yes</literal>, the network is deemed required when
-          determining whether the system is online when running
-          <command>systemd-networkd-wait-online</command>. When <literal>no</literal>, the network is ignored
-          when checking for online state. When a minimum operational state and an optional maximum operational
+          determining whether the system is online (including when running
+          <command>systemd-networkd-wait-online</command>). When <literal>no</literal>, the network is ignored
+          when determining the online state. When a minimum operational state and an optional maximum operational
           state are set, <literal>yes</literal> is implied, and this controls the minimum and maximum
           operational state required for the network interface to be considered online.
           Defaults to <literal>yes</literal>.</para>