It is probably true that this has not been seen much as a bug due to DNS normally being available, hence NIS dependency (if present) being a secondary issue. However, we found that ntp did not recover by itself, so possibly it only tries to find the nameservers once, but will re-try for the time servers in ntp.conf
I don't think it is necessary to test for any direct dependency on NIS in ntp.conf (that could be tricky) but a more robust approach would be to start (or restart?) ntp if a directory service is started/restarted just to make sure any such dependency or time-server changes are resolved. I presume this is the sort of thing Upstart can do. Incidentally it seems the last post for bug #604717 is spam, is there any way to get it deleted? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/999725 Title: broken start-up dependencies for ntp (starts before NIS is available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/999725/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
