Home

 


Re: NTP servers redundancy Posted on: Tue, 19 Jan 2010 15:46:09 -0600


>The fundamental problem with two servers is this: which one do you
>believe when the two differ? You know that at least one of the two must
>be wrong but it's impossible to determine WHICH one!

You get more than time from a packet exchange. You also get
a good idea of the accuracy. Two clocks can give (slightly)
different answers without either being wrong. If that happens
you can use either one.

The problem is that IF they give wildly different answers
(perhaps because one of them is broken) THEN you don't know
which one is good.

--
These are my opinions, not necessarily my employer's. I hate spam.
56517. Re: NTP servers redundancy
56518. Re: NTP servers redundancy
56519. Re: NTP servers redundancy
56520. Re: NTP servers redundancy
56521. Re: NTP servers redundancy
56522. Re: NTP servers redundancy
56523. Re: NTP servers redundancy
56524. Re: NTP servers redundancy
56525. Re: NTP servers redundancy
56526. Re: NTP servers redundancy
56527. Re: NTP servers redundancy
56528. Re: NTP servers redundancy
56529. Re: NTP servers redundancy
56530. Re: NTP servers redundancy
56531. Re: NTP servers redundancy
56532. Re: NTP servers redundancy
56533. Re: NTP servers redundancy
56534. Re: NTP servers redundancy
56535. Re: NTP servers redundancy
56536. Re: NTP servers redundancy