Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as triaged and let them handle it from here. Thanks
for taking the time to make Ubuntu better!

** Description changed:

  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

** Changed in: ntp (Ubuntu)
   Importance: Undecided => Low
       Status: Incomplete => Triaged

-- 
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

Reply via email to