[pkg-ntp-maintainers] Bug#683061: Bug#683061: ntp: diff for NMU version 1:4.2.6.p5+dfsg-2.1

Kurt Roeckx kurt at roeckx.be
Wed May 29 20:27:56 UTC 2013


On Wed, May 29, 2013 at 09:31:00PM +0200, Helmut Grohne wrote:
> Hi Kurt,
> 
> Now unbound[1] is a bit special when it comes to resolvconf (the
> package). It drops a file in /etc/resolvconf/update.d that causes it to
> be listed as the sole nameserver in /etc/resolv.conf. During boot
> /etc/resolv.conf is initially empty, because I didn't specify any name
> servers in /etc/network/interfaces. So at the time ntp starts, it likely
> find that there are no name servers. Only after unbound has started, the
> file is populated.
> 
> Can you tell me what ntp does when it fails to find any name servers?

If my memmory is any good, it listens to what in that getaddrinfo() returns.

Trying this with bind9 stopped, I see getaddrinfo return
EAI_SYSTEM.  This should be reacted on as a non-permant
error, so ntp should retry it.

But restarting ntp and looking in my log file, I see:
getaddrinfo: "0.debian.pool.ntp.org" invalid host address, ignored

This clearly isn't what I was expecting, and probably a bug in
ntpd.


Kurt



More information about the pkg-ntp-maintainers mailing list