[ntp:questions] Meinberg NTP client continuously resync to server

Mischanko, Edward T Edward.Mischanko at arcelormittal.com
Sun May 19 07:07:29 UTC 2013

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?


> -----Original Message-----
> From: questions-bounces+edward.mischanko=arcelormittal.com at lists.ntp.org
> [mailto:questions-
> bounces+edward.mischanko=arcelormittal.com at lists.ntp.org] On Behalf Of
> renoandy775 at gmail.com
> Sent: Friday, May 17, 2013 5:43 PM
> To: questions at lists.ntp.org
> 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
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions

More information about the questions mailing list