mirror of
https://github.com/systemd/systemd
synced 2024-10-15 04:24:19 +00:00
man: document what SIGUSR1 and SIGUSR2 do to resolved
This commit is contained in:
parent
bc81447ea5
commit
2c7284a9a9
|
@ -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>
|
||||
|
|
Loading…
Reference in a new issue