Aurelien Jarno 2738480a4b Fix failing nss/tst-nss-files-hosts-long with local resolver ... When a local resolver like unbound is listening on the IPv4 loopback address 127.0.0.1, the nss/tst-nss-files-hosts-long test fails. This is due to: - the default resolver in the absence of resolv.conf being 127.0.0.1 - the default DNS NSS database configuration in the absence of nsswitch.conf being 'hosts: dns [!UNAVAIL=return] file' This causes the requests for 'test4' and 'test6' to first be sent to the local resolver, which responds with NXDOMAIN in the likely case those records do no exist. In turn that causes the access to /etc/hosts to be skipped, which is the purpose of that test. Fix that by providing a simple nsswitch.conf file forcing access to /etc/hosts for that test. I have tested that the only changed result in the testsuite is that test.		2021-09-07 21:41:38 +02:00
..
host.conf	nss: tst-nss-files-hosts-long: Add host.conf [BZ #21915]	2019-02-21 16:02:29 -05:00
hosts	nss: Add tst-nss-files-hosts-long test [BZ #21915]	2019-02-08 14:38:27 -05:00
nsswitch.conf	Fix failing nss/tst-nss-files-hosts-long with local resolver	2021-09-07 21:41:38 +02:00