summaryrefslogtreecommitdiffstats
path: root/man/nss-mymachines.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-04-15 18:15:51 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-04-16 12:13:42 +0200
commitf2a20e9966d48d460e50ab36d46e63277177878c (patch)
tree8448a49ebd5d6d0aeff875dfc3fa0793ecc66993 /man/nss-mymachines.xml
parentman: move "files" after "resolve" in the suggested configuration (diff)
downloadsystemd-f2a20e9966d48d460e50ab36d46e63277177878c.tar.xz
systemd-f2a20e9966d48d460e50ab36d46e63277177878c.zip
man: move "myhostname" right after "resolve"
The text in the man page provides the justification why I think this is generally the right thing. An additional reason is that with the previous commit (to move resolved earlier), since resolved internally implements the same rules that nss-myhostname does, we'd have this strange inversion where the priority of external configuration would be different in the "resolve" path and in the fallback path.
Diffstat (limited to 'man/nss-mymachines.xml')
-rw-r--r--man/nss-mymachines.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/nss-mymachines.xml b/man/nss-mymachines.xml
index 71865874dd..1ff88aba2d 100644
--- a/man/nss-mymachines.xml
+++ b/man/nss-mymachines.xml
@@ -69,7 +69,7 @@
group: compat <command>mymachines</command> systemd
shadow: compat
-hosts: <command>mymachines</command> resolve [!UNAVAIL=return] files dns myhostname
+hosts: <command>mymachines</command> resolve [!UNAVAIL=return] myhostname files dns
networks: files
protocols: db files