diff options
author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-06-12 18:28:30 -0400 |
---|---|---|
committer | GitHub <noreply@github.com> | 2016-06-12 18:28:30 -0400 |
commit | af4ddf529e5e172962a668fac0bbe2305a2e24a5 (patch) | |
tree | 0d1ca129ba7519d1b6361fbe387b6278f2a497d0 /man/systemd-resolved.service.xml | |
parent | 7f401340b0cfd680a996c89cf2ccfe1b445b34ef (diff) | |
parent | 04b764bf76a74943ca652691cfd5b511ed8fe96c (diff) |
Merge pull request #3502 from poettering/resolved-flush-cache
resolved: allow clients request cache flushes
Diffstat (limited to 'man/systemd-resolved.service.xml')
-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>, |