C de-Avillez <hgg...@gmail.com> writes: > OK. I found the upstream bug on this. Please note that -- per upstream > -- this is still open. The issue stems from a *non-working* DNS at the > time NTP is triggered (most probably on boot).
The boot time issue is not what is happening for me. Retarting the ntpd daemon using the /etc/init.d/ntp script when DNS is known to be working still fails. Running it from the command line as previously mentioned still fails. Since I can get the upstream ntp-4.2.6 release to fail, I am going to try to debug that rather than the 4.2....@1.1620-0 lucid version, unless you some need otherwise. My guess would be it involves a memory leak, although I would assume the code in deamon programs like ntpd are very closely examined. I can't otherwise explain why a program that works from /home/util64/ntp-4.2.6/bin would fail when moved to /usr/sbin. Nobody else seems to have the problem with Lucid, and there is a simple fix to get it working, if someone else reports the problem. -- Barry Fishman -- ntp host name not found error https://bugs.launchpad.net/bugs/548885 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
