ntpdate should not hold on to the port after it's completed updating the clock, so starting ntpdate before ntpd should not be a problem as long as ntpdate has completed its update. If it is, then we have a buggy ntpdate. I have seen other Linux distributions do this with no problems at all in getting ntpdate/ntpd to coexist. In fact, since ntpd may refuse to synchronize the clock if it's very far off the network time, it is a good idea to use ntpdate to "preset" the clock before starting ntpd. The man page for ntpdate actually recommends this:
"ntpdate can be run manually as necessary to set the host clock, or it can be run from the host startup script to set the clock at boot time. This is useful in some cases to set the clock initially before starting the NTP daemon ntpd." It appears that maybe there's a parallel startup problem happening, where the ntpdate isn't given time to complete its work before ntpd starts up, or there may be a bug in the version of ntpdate in Ubuntu. -- Ntp doesn't synchronise on startup in Gutsy https://bugs.launchpad.net/bugs/158110 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
