I know it's a long time, but I'm cleaning up old NTP bugs atm. But despite its age it is something that still applies :-/ - IMHO I agree and it should be -B to be safe no matter what the time diff is - probably while at it also -s to go to syslog (equivalent) - I think it is not worth a delta or SRU, so it should be reported and fixed in Debian to be picked up on the next merge
The only "good" on that is that ntpdate: - isn't installed by default anymore (systemd now handles time updates by default) - even if so in the default config fails if ntp is installed as well sed -rne 's/^(servers?|peer)[[:space:]]+(-[46][[:space:]]+)?([-_.:[:alnum:]]+).*$/\3/p' "/etc/ntp.conf" | grep -v '^127\.127\.' doesn't work anymore in /usr/sbin/ntpdate-debian That causes the issue itself to show up less, but then is a bug on its own that should be fixed Raising prio and subscribing to come back and take a look at it. ** Changed in: ntp (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/75347 Title: ntp script steps time Status in ntp package in Ubuntu: Triaged Bug description: Distro Release: Dapper Package: ntp Description: The clock of one of my routers running Dapper had bogus time (something that ntpd was slowly but steadily working on). Then I added an interface and boom! the time was stepped. OSPF went into an retarded state, loosing random routes and everything was going crazy. After the ordeal was over I found the /etc/network/if-up.d/ntpdate script, where time is stepped _every_ time interfaces go up/down. This is probably okay on a laptop or something, but it's madness to do so on a server. I sure know OSPF isn't the only service that gets really confused when the clock leaps. There's actually a reason why the manual page of ntpdate says the following about the -b option: «This option should be used when called from a startup file at boot time.» I've now deinstalled ntpdate (it served no purpose anyway since I have ntpd), but really, this package should not be part of the default server installation with this behaviour. DESIRED FIX: 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. Tore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/75347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
