>The log file shows ntp is started before ntpdate. Therefore, when ntpdate gets >started, the ntp socket is already in use, ntpdate fails and the clock can not >be corrected immediately. I can reproduce this on my own Gutsy system, when >roaming mode is used. >This looks like ntp should be started at a higher rc.d sequence number.
Do Not Do That! On my machine (Gutsy) precisely the reverse happens: ntpdate starts before ntpd, and it’s ntpd that can’t bind to the socket. This causes ntpd not to start, so I end up with unsynchronized clock. If there’s an ntpd, ntpdate must not start *at all*. I have removed the execute permission on /etc/network/if-up.d/ntpdate, and now everything works perfectly, with ntpd taking care of the clock. -- 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
