diff options
| author | Landon Fuller <landonf@bikemonkey.org> | 2013-02-16 22:57:40 -0500 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2013-02-17 07:06:36 +0100 |
| commit | 6dfb35f3ff7ad2d2089c0a3e5eab342384e45e4c (patch) | |
| tree | d5ed356d6aeb395e0453b83e66b70f2404387a9b /install_with_python.sh | |
| parent | 05235d5b444558f6d06ef12ea7d74850800425cf (diff) | |
| download | samba-6dfb35f3ff7ad2d2089c0a3e5eab342384e45e4c.tar.gz samba-6dfb35f3ff7ad2d2089c0a3e5eab342384e45e4c.tar.bz2 samba-6dfb35f3ff7ad2d2089c0a3e5eab342384e45e4c.zip | |
Fallback to the internal resolver on EAI_FAIL.
On Linux, non-RFC 1034-complaint names (such as gc._msdsc.example.org)
will result in the resolver returning the non-POSIX EAI_NODATA. In that
case, the case statement here would fall back on the internal resolver,
allowing resolution to complete successfully.
On FreeBSD, the libc resolver uses the same validation code, but
the POSIX result of EAI_FAIL is returned instead of EAI_NODATA. Since
there was no case for this error code, no fallback to the internal
resolver would occur. This led to replication failing on FreeBSD.
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Autobuild-User(master): Andrew Bartlett <abartlet@samba.org>
Autobuild-Date(master): Sun Feb 17 07:06:36 CET 2013 on sn-devel-104
Diffstat (limited to 'install_with_python.sh')
0 files changed, 0 insertions, 0 deletions