*** This bug is a duplicate of bug 1206164 ***
https://bugs.launchpad.net/bugs/1206164
Chasing down more bugs I came by recently there is a lot of pro/con
about this.
The Summary related to this bug is:
The general behavior is depending on the time difference. If the time
differences off a lot it (has to) step time, otherwise (which should be what
happens) it drifts. It is considered valid configured time sources that a new
change should not cause a huge new diff.
For environments where this "considered to be normal" case does not
apply we will provide an option to disable the auto-update. I'll dup
this (be aware that on recent releases one has to care about timedatectl
separately if that is used instead of ntpdate).
** This bug has been marked a duplicate of bug 1206164
/etc/network/if-up.d/ntpdate does not detach correctly
--
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
