summaryrefslogtreecommitdiff
path: root/units/sockets.target
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2016-10-24 18:58:03 +0200
committerLennart Poettering <lennart@poettering.net>2016-10-24 19:04:43 +0200
commit75555c2824fde73bde83f78d160a4f50482bc160 (patch)
tree12d6f27883df38613239859d9096e607026385ce /units/sockets.target
parent344874fcd0a3fc1f9bc6cdf34ecaf537c10a3ad3 (diff)
man: sync up the suggested nsswitch.conf configuration for our four NSS modules
This unifies the suggested nsswitch.conf configuration for our four NSS modules to this: hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname Note that this restores "myhostname" to the suggested configuration of nss-resolve for the time being, undoing 4484e1792b64b01614f04b7bde97bf019f601bf9. "myhostname" should probably be dropped eventually, but when we do this we should do it in full, and not only drop it from the suggested nsswitch.conf for one of the modules, but also drop it in source and stop referring to it altogether. Note that nss-resolve doesn't replace nss-myhostname in full: the former only works if D-Bus/resolved is available for resolving the local hostname, the latter works in all cases even if D-Bus or resolved are not in operation, hence there's some value in keeping the line as it is right now. Note that neither dns nor myhostname are considered at all with the above configuration unless the resolve module actually returns UNAVAIL. Thus, even though handling of local hostname resolving is implemented twice this way it is only executed once for each lookup.
Diffstat (limited to 'units/sockets.target')
0 files changed, 0 insertions, 0 deletions