I think you need to first ask yourself how much of an offset is acceptable. The default for a step adjustment is 0.128 seconds, but this value can be tinkered in the ntp.conf file with the following command:
tinker step .005 Going below 0.005 seconds doesn't seem practical as ntp will not slew the time when the offset is above the step setting. Since slewing the time is preferred, how much of an offset is acceptable to you? Regards, Ed > -----Original Message----- > From: questions-bounces+edward.mischanko=arcelormittal....@lists.ntp.org > [mailto:questions- > [email protected]] On Behalf Of > [email protected] > Sent: Friday, May 17, 2013 5:43 PM > To: [email protected] > Subject: [ntp:questions] Meinberg NTP client continuously resync to server > > I am using the Meinberg ntpd 4.2.4 deamon to syncronize a client pc to > another server pc on my network. The client time cannot be trusted. > The problem I am having is that if the client time drifts out too far as a > result of a network loss, it does not appear to resync and correct its > clock to conform to the server's true time. > > Does anyone know how to configure this application to have the client > always bust and update its clock to lock onto the NTP server ? > > > _______________________________________________ > questions mailing list > [email protected] > http://lists.ntp.org/listinfo/questions _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
