On 19/01/13 06:36, Neil Bothwick wrote: > On Fri, 18 Jan 2013 18:08:50 +0000 (UTC), Grant Edwards wrote: > >>>> By default, ntpd doesn't seem to want to do >>>> a step correction to fix large clock errors on startup (there's >>>> probably an option for that). >>> >>> That's for ntp-client to do. >> >> In additon to being a server, ntpd _is_ an ntp client. > > But ntpd will not handle large jumps in time, such as when booting with a > broken CMOS clock. So you run /etc/init.d/ntp-client as well, which gets > the clock right at boot time, then ntpd can keep it right. > >> Are you talking about running ntpclient >> (http://doolittle.icarus.com/ntpclient) instead of ntpd? > > No. > > % qlist net-misc/ntp | grep init.d > /etc/init.d/ntpd > /etc/init.d/ntp-client > >
It can handle large jumps, check out this in the "man ntp.conf": tinker panic 0 or the -g option to ntpd (again, its in a man page.) Basicly, you just need to read and configure it ... I have it working even on a raspberry pi which has HW clock :) Even the slew rate, or slew/jump can be set. BillK
