diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2020-04-15 18:15:51 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2020-04-16 12:13:42 +0200 |
| commit | f2a20e9966d48d460e50ab36d46e63277177878c (patch) | |
| tree | 8448a49ebd5d6d0aeff875dfc3fa0793ecc66993 /man/nss-resolve.xml | |
| parent | 44b7aedbde8b30825ee1dbf47346d21007a1a417 (diff) | |
| download | systemd-f2a20e9966d48d460e50ab36d46e63277177878c.tar.gz | |
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-resolve.xml')
| -rw-r--r-- | man/nss-resolve.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/nss-resolve.xml b/man/nss-resolve.xml index 5c8b745881..cc33b2c082 100644 --- a/man/nss-resolve.xml +++ b/man/nss-resolve.xml @@ -67,7 +67,7 @@ group: compat mymachines systemd shadow: compat -hosts: mymachines <command>resolve [!UNAVAIL=return]</command> files dns myhostname +hosts: mymachines <command>resolve [!UNAVAIL=return]</command> myhostname files dns networks: files protocols: db files |