diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-06-10 20:29:32 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-06-10 23:26:53 +0200 |
commit | 2c7284a9a966a7790cb260e89428db5bb2020eef (patch) | |
tree | 390cf9cd5856c9e530de45d7c076750e6668e6de | |
parent | bc81447ea556586b09226ce2d3fe375a7adc2c16 (diff) |
man: document what SIGUSR1 and SIGUSR2 do to resolved
-rw-r--r-- | man/systemd-resolved.service.xml | 22 |
1 files changed, 22 insertions, 0 deletions
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 @@ -146,6 +146,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> <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |