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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/75347 Title: ntp script steps time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/75347/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
