there is some people who use ntpd who don't want any disruptive
adjustment. If you really think that should be changed could you open a
bug upstream which is the right place to discuss the behaviour for the
tool? We have thousand of bugs open a few people working on them at the
moment which means i
I understand the mechanics now but wouldn't it make more sense to run
ntpdate before starting ntpd? My clock was off by almost 18 hours once
ntpd started. The standard ntp polling interval is 64 seconds and the
maximum clock shift is 128ms. At that rate, it will take weeks to shift
to the correc
Thank you for your bug, that's not a bug, you can use either ntp which
is slowly adjusting the clock or using ntpdate to force a sync, ntpdate
is activate only if you are not using ntp. Closing the bug, that's done
that way by design, that's not a bug
** Changed in: gnome-system-tools (Ubuntu)
Forgot to mention. I'm on Feisty amd64 with latest updates (Jan 22,
2007).
--
NTP installs but does not update
https://launchpad.net/bugs/80933
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
