diff options
| author | Yu, Li-Yu <afg984@gmail.com> | 2019-03-04 05:50:22 +0800 |
|---|---|---|
| committer | Martin Pitt <martinpitt@users.noreply.github.com> | 2019-03-03 22:50:22 +0100 |
| commit | abfa5697fa94f31166b2268ae0f5c6b37cdad935 (patch) | |
| tree | c184e02f94e07e9e8432c994dd410ec6dadf0b7a /man/systemd-resolved.service.xml | |
| parent | bdc8f36bfb84b1213fa9affe46f46e6dc160d56d (diff) | |
| download | systemd-abfa5697fa94f31166b2268ae0f5c6b37cdad935.tar.gz | |
man: flush-caches and reset-server-features are commands for resolvectl (#11877)
Diffstat (limited to 'man/systemd-resolved.service.xml')
| -rw-r--r-- | man/systemd-resolved.service.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index d7334e01ec..190bd2e451 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -249,7 +249,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>resolvectl --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> @@ -263,7 +263,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>resolvectl --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> |