Thanks for the bug report.
I'm closing this bug because it has been fixed in Edgy.
If you need a fix for this bug in Dapper, please follow the
instructions in the "How to request new packages" section of the
Backports wiki page:
https://wiki.ubuntu.com/UbuntuBackports
** Description changed:
- Binary package hint: ntp
+ Distro Release: Dapper
+ Package: ntp
- 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.
+ 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.
Tore
** Changed in: ntp (Ubuntu)
Status: Unconfirmed => Rejected
--
ntp script steps time
https://launchpad.net/bugs/75347
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
