[ntp:questions] ntpd keep trying preferred servers?
Richard B. Gilbert
rgilbert88 at comcast.net
Wed Sep 7 19:59:56 UTC 2011
On 9/7/2011 10:45 AM, Seth Seeger wrote:
> On Wednesday, September 7, 2011 10:37:18 AM UTC-4, Rob wrote:
>> Steve Kostecke<kost... at ntp.org> wrote:
>>> Without a real time reference your server clock is "freewheeling" and
>>> most likely not ticking at a stable or fixed rate. So rds are
>>> continually converging on a moving target.
>> This is exactly what some people need. Same time between different
>> servers in the network, don't care if it is UTC or not.
>> When it is not your requirement, fine. But stop suggesting others
>> it is no good.
> I understand that I may be freewheeling. It's not ideal, but the real requirement is that the server and rds stay perfectly in sync.
> Is there a better way to do this? Should I set it up with peers instead of one server and two clients?
It's MUCH easier to stay in sync when the server is marching along at
EXACTLY one second per second. Transmitting time via the Internet
introduces a great deal of noise! I use a Motorola GPS Timing Receiver
for this reason.
More information about the questions