"Joseph Gwinn" <joegw...@comcast.net> wrote in message
news:joegwinn-ee48fd.22434621102...@news.giganews.com...
In article <i9pkvb$dc...@news.eternal-september.org>,
"David J Taylor" <david-tay...@blueyonder.co.uk.invalid> wrote:
[]
You might consider providing a local, more precise NTP server with
something like a small, fan-less Intel Atom system running FreeBSD and
synched across the network to your GPS time server. You might be able
to
keep a small box like that in a more temperature controlled
environment,
but even without it might provide a way of smoothing out any jitter due
to
your remote connection to the GPS server.
I'm not convinced that this would help. NTP reports a round trip time
of slightly more than 2 mS, which is very close to the two milliseconds
that ping sees, so it seems unlikely that the time server or intervening
network is the root cause.
[]
Joe Gwinn
No, I wasn't convinced either - hence it was just a suggestion. On the
systems here, though, the NTP delay shows around 0.25-0.75 msec to the LAN
servers.
Your other points noted.
Cheers,
David
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
