From bfe522304da217296e2a61040f58e35ec5d6f3f2 Mon Sep 17 00:00:00 2001
From: Michael Biebl <biebl@debian.org>
Date: Mon, 16 Aug 2021 09:51:46 +0200
Subject: New upstream version 1.30.6

---
 man/nmcli.xml | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 61 insertions(+)

(limited to 'man/nmcli.xml')

diff --git a/man/nmcli.xml b/man/nmcli.xml
index b0665efd..bc72c311 100644
--- a/man/nmcli.xml
+++ b/man/nmcli.xml
@@ -356,6 +356,7 @@
         <arg choice='plain'><command>hostname</command></arg>
         <arg choice='plain'><command>permissions</command></arg>
         <arg choice='plain'><command>logging</command></arg>
+        <arg choice='plain'><command>reload</command></arg>
       </group>
       <arg rep='repeat'><replaceable>ARGUMENTS</replaceable></arg>
     </cmdsynopsis>
@@ -419,6 +420,66 @@
           for available level and domain values.</para>
         </listitem>
       </varlistentry>
+
+      <varlistentry>
+        <term>
+          <command>reload</command>
+          <arg rep='repeat'><replaceable>flags</replaceable></arg>
+        </term>
+
+        <listitem>
+          <para>
+            Reload NetworkManager's configuration and perform certain
+            updates, like flushing caches or rewriting external state to
+            disk. This is similar to sending SIGHUP to NetworkManager
+            but it allows for more fine-grained control over what to
+            reload through the flags argument. It also allows non-root
+            access via PolicyKit and contrary to signals it is
+            synchronous. Available flags are:
+          </para>
+          <variablelist>
+            <varlistentry>
+              <term><option>conf</option></term>
+              <listitem><para>
+                Reload the NetworkManager.conf configuration from
+                disk. Note that this does not include connections, which
+                can be reloaded through <command>nmcli connection
+                reload</command> instead.
+              </para></listitem>
+            </varlistentry>
+
+            <varlistentry>
+              <term><option>dns-rc</option></term>
+              <listitem><para>
+                Update DNS configuration, which usually involves writing
+                /etc/resolv.conf anew. This is equivalent to sending the
+                SIGUSR1 signal to the NetworkManager process.
+              </para></listitem>
+            </varlistentry>
+
+            <varlistentry>
+              <term><option>dns-full</option></term>
+              <listitem><para>
+                Restart the DNS plugin. This is for example useful when
+                using dnsmasq plugin, which uses additional
+                configuration in
+                <filename>/etc/NetworkManager/dnsmasq.d</filename>. If
+                you edit those files, you can restart the DNS
+                plugin. This action shortly interrupts name resolution.
+              </para></listitem>
+            </varlistentry>
+          </variablelist>
+          <para>
+            With no flags, everything that is supported is reloaded,
+            which is identical to sending a SIGHUP. See
+            <citerefentry>
+              <refentrytitle>NetworkManager</refentrytitle>
+              <manvolnum>8</manvolnum>
+            </citerefentry>
+            for more details about signals.
+          </para>
+        </listitem>
+      </varlistentry>
     </variablelist>
   </refsect1>
 
-- 
cgit 1.3.0-6-gf8a5