I'm sorry.. I meant almost immediate in comparison to the nist servers, which often never sync. It does take a couple of minutes to get there with the non nist servers. We're not using burst mode, but polling every 16 seconds.
On Fri, Feb 1, 2019, 10:46 AM Majdi S. Abbas <m...@latt.net wrote: > On Wed, Jan 30, 2019 at 01:23:42PM -0800, eli...@espoc.com wrote: > > We're having issues syncing to all nist servers: > > https://tf.nist.gov/tf-cgi/servers.cgi > > > > But are easily able to sync to time.google.com and pool.ntp.org. > > > > ntpq -p shows reach numbers that clearly indicate intermittent failures > (even numbers etc) > > when going against any nist server (including time.nist.gov, but zero > failures and almost > > immediate reach of 377 when syncing to pool.ntp.org or time.google.com. > > Immediate 377? > > Are you using burst mode? > > --msa > _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
