Steve Langasek <steve.langa...@canonical.com> writes: > I'm unclear about the meaning of your last message. How is ntp being > told to aim at different NTP servers if you /do/ restart it? The > default, static configuration shipped with the ntp package always points > to ntp.ubuntu.com; how do you have ntp configured such that restarting > the process makes a difference in where it's syncing to?
As just one obvious answer, consider dhcp getting a new ntp server -- you do realize that dhcp changes your configured ntp servers, right? -- although it appears this has gone on so long that the dhcp exit hooks from Jaunty now seem restart the ntp server (as you would know if you looked into this.) Consider also that ntpd did not traditionally notice that interfaces had come and gone and thus would not have any ability to talk to the ntp server if it was not restarted, although again, the ntpd shipped with Jaunty does this correctly. This and more is explained well enough in the bug report for someone who understands the underlying problem. Anyway, all of this remains an issue on Hardy and possibly on Intrepd, but as I no longer run any such boxes I no longer care. It might still be an issue on Jaunty for some corner cases but I haven't been paying attention -- Jaunty is too new, and given how long it has been I haven't even looked at all the scripts currently involved -- nothing quite like having a bug report ignored for this long. Perry -- Perry E. Metzger pe...@piermont.com -- ntp daemon not reconfigured by /etc/network https://bugs.launchpad.net/bugs/120199 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
