From 2c7284a9a966a7790cb260e89428db5bb2020eef Mon Sep 17 00:00:00 2001
From: Lennart Poettering <lennart@poettering.net>
Date: Fri, 10 Jun 2016 20:29:32 +0200
Subject: man: document what SIGUSR1 and SIGUSR2 do to resolved

---
 man/systemd-resolved.service.xml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

(limited to 'man')

diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 829729ca09..485f3e9aee 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -145,6 +145,28 @@
 
   </refsect1>
 
+  <refsect1>
+    <title>Signals</title>
+
+    <variablelist>
+      <varlistentry>
+        <term><constant>SIGUSR1</constant></term>
+
+        <listitem><para>Upon reception of the SIGUSR1 process signal <command>systemd-resolved</command> will dump the
+        contents of all DNS resource record caches it maintains into the system logs.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
+        <term><constant>SIGUSR2</constant></term>
+
+        <listitem><para>Upon reception of the SIGUSR2 process signal <command>systemd-resolved</command> will flush all
+        caches it maintains. Note that it should normally not be necessary to request this explicitly – except for
+        debugging purposes – as <command>systemd-resolved</command> flushes the caches automatically anyway any time
+        the host's network configuration changes.</para></listitem>
+      </varlistentry>
+    </variablelist>
+  </refsect1>
+
   <refsect1>
     <title>See Also</title>
     <para>
-- 
cgit v1.2.3-54-g00ecf