|author||Rich Felker <firstname.lastname@example.org>||2015-10-26 18:42:22 -0400|
|committer||Rich Felker <email@example.com>||2015-10-26 18:42:22 -0400|
safely handle failure to open hosts, services, resolv.conf files
previously, transient failures like fd exhaustion or other resource-related errors were treated the same as non-existence of these files, leading to fallbacks or false-negative results. in particular: - failure to open hosts resulted in fallback to dns, possibly yielding EAI_NONAME for a hostname that should be defined locally, or an unwanted result from dns that the hosts file was intended to replace. - failure to open services resulted in EAI_SERVICE. - failure to open resolv.conf resulted in querying localhost rather than the configured nameservers. now, only permanent errors trigger the fallback behaviors above; all other errors are reportable to the caller as EAI_SYSTEM.
Diffstat (limited to 'arch/arm')
0 files changed, 0 insertions, 0 deletions