From: Zbigniew Jędrzejewski-Szmek Date: Sun, 22 Jun 2014 15:50:33 +0000 (-0400) Subject: man: untabify systemd-resolved.service.xml X-Git-Tag: v215~224 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=c305edb643130cbb2a9cc1414c216e21d227f32f man: untabify systemd-resolved.service.xml --- diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 517e08ef2..839f46a12 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -58,24 +58,24 @@ systemd-resolved is a system service that manages network name resolution. It does so by - generating /run/systemd/resolve/resolv.conf, - which may be symlinked from /etc/resolv.conf. - The contents is generated from the global settings in + generating /run/systemd/resolve/resolv.conf, + which may be symlinked from /etc/resolv.conf. + The contents is generated from the global settings in resolved.conf5, - the per-link static settings in .network files, - and the per-link dynamic settings received over DHCP. See + the per-link static settings in .network files, + and the per-link dynamic settings received over DHCP. See systemd.network5 - for more details. + for more details. Note that /run/systemd/resolve/resolv.conf should not be used directly, but only through a symlink from - /etc/resolv.conf. + /etc/resolv.conf. See Also - resolved.conf5, + resolved.conf5, systemd1, systemd.network5, systemd-networkd.service8