summaryrefslogtreecommitdiff
path: root/man/systemd-resolved.service.xml
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2018-04-19 03:25:25 +0900
committerYu Watanabe <watanabe.yu+github@gmail.com>2018-04-19 03:25:25 +0900
commitb69f810c8a2ece4e44c1b1898e237bb671b36a21 (patch)
treec7f431b1014512f3c4062f132d274bd86077d9dc /man/systemd-resolved.service.xml
parenta7a4c60a253a181385764bcb542906a312b68fe9 (diff)
downloadsystemd-b69f810c8a2ece4e44c1b1898e237bb671b36a21.tar.gz
man: create man page for resolvectl
Diffstat (limited to 'man/systemd-resolved.service.xml')
-rw-r--r--man/systemd-resolved.service.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index fcc39a554e..9ca1133fed 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -216,7 +216,7 @@
<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. Sending this signal
- to <command>systemd-resolved</command> is equivalent to the <command>systemd-resolve --flush-caches</command>
+ to <command>systemd-resolved</command> is equivalent to the <command>resolvectl --flush-caches</command>
command, however the latter is recommended since it operates in a synchronous way.</para></listitem>
</varlistentry>
@@ -230,7 +230,7 @@
should normally not be necessary to request this explicitly – except for debugging purposes – as
<command>systemd-resolved</command> automatically forgets learnt information any time the DNS server
configuration changes. Sending this signal to <command>systemd-resolved</command> is equivalent to the
- <command>systemd-resolve --reset-server-features</command> command, however the latter is recommended since it
+ <command>resolvectl --reset-server-features</command> command, however the latter is recommended since it
operates in a synchronous way.</para></listitem>
</varlistentry>
</variablelist>
@@ -244,7 +244,7 @@
<citerefentry><refentrytitle>resolved.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>dnssec-trust-anchors.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>nss-resolve</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
- <citerefentry><refentrytitle>systemd-resolve</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>resolvectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry project='man-pages'><refentrytitle>hosts</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>,