On Sun, Jun 26, 2011 at 09:05:59PM +0100, David Woolley wrote:
If the jitter is of the order of 500 microseconds, and your
delays are perfectly symmetric, and there is no clock wander (in
particular, the temperature is tightly controlled), the error will
exceed 500 microseconds, a small but
In our NTP client-server setup which is done locally, we've 3 servers each made
to synchronize with its own local clock only.
The client is having the entries of these 3 servers. The following is the
output snippet of ntpq -p taken over a period of 1 hour at regular intervals of
5 seconds.
Mischanko, Edward T wrote:
As for my question on server selection, all these servers
are routers on a corporate network.
If 6 servers have the same offset and 3 do not which
ones would you choose?
I choose the 6 servers with the same offset.
Which would NTP choose?
You are likely
Hello, Is anyone understanding what I am saying?
Did you see the ntpq -p post that shows the server with high jitter and
high offset selected?
What I am saying is that the various algorithms don't neccisarily work
as described.
-Original Message-
From:
On 6/24/2011 2:45 AM, Pranay Kumar Srivastava wrote:
In our NTP client-server setup which is done locally, we've 3 servers each made
to synchronize with its own local clock only.
First mistake!! The local clock is an extremely poor time keeper.
The client is having the entries of these 3
On 2011-06-24, Pranay Kumar Srivastava pranay.shrivast...@hcl.com
wrote:
In our NTP client-server setup which is done locally, we've 3 servers
each made to synchronize with its own local clock only.
ntpd never synchronizes to the local clock (really the Undisciplined
Local Clock or Orphan
