Bug#618315: Acknowledgement (libsocket-getaddrinfo-perl: README.Debian misrepresents the nature of the bin/get{addr, name}info binaries)

[Paul LeoNerd Evans]

In fact, case in point... The reason I was wanting to use getaddrinfo in
the first place, was to debug why a server of mine was listening on
[::1] rather than 127.0.0.1; the relevant output was:

---

$ getaddrinfo --passive --service 8034
Resolved host '', service '8034'

socket(AF_INET , SOCK_STREAM, IPPROTO_TCP) + '0.0.0.0:8034'
socket(AF_INET , SOCK_DGRAM , IPPROTO_UDP) + '0.0.0.0:8034'
socket(AF_INET , SOCK_RAW   , IPPROTO_IP ) + '0.0.0.0:8034'
socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP) + '[::]:8034'
socket(AF_INET6, SOCK_DGRAM , IPPROTO_UDP) + '[::]:8034'
socket(AF_INET6, SOCK_RAW   , IPPROTO_IP ) + '[::]:8034'

$ getaddrinfo --service 8034
Resolved host '', service '8034'

socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP) + '[::1]:8034'
socket(AF_INET6, SOCK_DGRAM , IPPROTO_UDP) + '[::1]:8034'
socket(AF_INET6, SOCK_RAW   , IPPROTO_IP ) + '[::1]:8034'
socket(AF_INET , SOCK_STREAM, IPPROTO_TCP) + '127.0.0.1:8034'
socket(AF_INET , SOCK_DGRAM , IPPROTO_UDP) + '127.0.0.1:8034'
socket(AF_INET , SOCK_RAW   , IPPROTO_IP ) + '127.0.0.1:8034'

---

This sort of direct observation of glibc's behaviour is not possible
using 'dig' or 'nslookup'.

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20110314/4ef20a19/attachment.pgp>