[pkg-ntp-maintainers] Bug#571469: Bug#571469: Will ntpd notice it can resolve after some time?

[Kurt Roeckx]

On Sun, Jun 13, 2010 at 03:09:56AM +0200, Regid Ichira wrote:
> 
>   I had the issue in 571469 here after using parallel booting for the first time.
> Am I right that the problem is that ntpd can not resolve names?  Will ntpd be able to
> notice, by itself, after some time, that it can resolve names?  With the old booting
> sequence, was ntpd started after bind?  Do we need one more Required-Start option, 
> namely $resolver?

It should figure this out after some time, if other software on
the system doesn't tell ntpd otherwise.  It should start a slave
process to do so.  There are currently 2 issues I'm aware of that
might cause some issues, causing it to return wrong info for
hostname lookups:
- libnss-mdns: #561622
- libc6: #582916

Atleast the libc6 issue alone still makes ntpd behave properly
it my case.  It will log a message: "host name not found", but
it will not add "(permanent)" after it, and it keeps working.

However, it would be nice that the if the network is up, that it's
actually useful.  We currently wait for:
$network $remote_fs $syslog

And it's my understanding that this should be enough, atleast
that's what I've been told when we added those.  If it's not
doing what it should, I suggest you file a bug against sysv-rc
or something.

If you still think there is an issue with ntpd please open a
new bug.  This one is about a configuration problem and
has been closed.


Kurt