* Hew > Thank you for taking the time to report this bug and helping to make > Ubuntu better. You reported this bug a while ago and there hasn't been > any activity in it recently. We were wondering is this still an issue > for you? Can you try with the latest Ubuntu release, Hardy Heron? Thanks > in advance.
Hello, since I now deinstall ntpdate on all servers I administer (better safe than sorry, and ntpd takes care of clock synch anyway) I've had no further problems caused by this. Reading /etc/network/if-up.d/ntpdate on my Hardy desktop, it does seem to still be the case that the time is unconditionally stepped whenever an interface is brought up/down: > # This is a heuristic: The idea is that if a static interface is brought > # up, that is a major event, and we can put in some extra effort to fix > # the system time. Feel free to change this, especially if you regularly > # bring up new network interfaces. > if [ "$METHOD" = static ]; then > OPTS="-b" > fi > > invoke-rc.d --quiet ntp stop || true > > /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null > > invoke-rc.d --quiet ntp start || true > > ) & So if you 1) run a service that is sensitive to time stepping, and 2) change some network interfaces runtime, this could still cause you problems. When it hit me it was Quagga/ospfd that got confused, and it was (not surprisingly) running on a firewall/router machine where network reconfiguration happens often. In my humble opinion use of the «-b» option should be dropped from server installs, or (even better) ntpdate should be run only as part of the bootup sequence, leaving clock synch to ntpd afterwards. Regards, -- Tore Anderson -- ntp script steps time https://bugs.launchpad.net/bugs/75347 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
