[Bug 356948] Re: Time is not set

[Jakob Unterwurzacher]

Looking at the debian bug, it seems the problem is:

1) openntpd uses adjtime(). This means the clock will not be set to the new time, but it sped up or slewed until the correct time is reached. That can take a long log time (7 days for 300 seconds).
So this:
> Apr 7 12:50:47 hardy2 ntpd[3453]: adjusting local clock by -20.540812s
> But the clock is *not* updated.
is NOT a bug. It will just take some time to adjust the clock.

2) openntpd on linux does not correct clock drift. The man page says it
uses adjfreq() to do so, which is not availible on linux.

3) If your clock drift is worse than what adjtime() can correct, your
clock will drift away. See for example http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=380737 .

Conclusion:
Don't use openntpd on linux.

** Bug watch added: Debian Bug tracker #380737
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380737

** Summary changed:

- Time is not set
+ Time adjustment is slow or fails in the face of clock drift

-- 
Time adjustment is slow or fails in the face of clock drift
https://bugs.launchpad.net/bugs/356948
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs