Thankyou sir!<br><br>As noted by Matthew, anyone needing that level of resolution should be doing it themselves, but I&#39;d love to see how a real world NTP implementation on the network here in NZ stacks up against local GPS unit so every little bit of info helps.<br>
<br>Cheers - N<br><br><br><div class="gmail_quote">On 3 September 2010 17:16, Jay Daley <span dir="ltr">&lt;<a href="mailto:jay@nzrs.net.nz">jay@nzrs.net.nz</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;"><br><div><div class="im"><div>On 3/09/2010, at 4:58 PM, Neil Gardner wrote:</div><br><blockquote type="cite">I think the issue is that with 3 clocks, if 1 fails, you are left in a situation where NTP can&#39;t tell which remaining clock to trust.<br>
<br>I&#39;d also be interested to know precisely where the servers are physically connected. While NTP is really very good at dealing with latency, it can&#39;t deal with asymmetry in the forward and return paths (it assumes one way delay = 0.5xRTT). I&#39;d be curious to see how many people have symmetric routes to the servers.<br>
</blockquote><div><br></div></div><div>We should be able to add what you need to the web site without giving away the exact physical location.</div><div><br></div><font color="#888888"><div>Jay</div></font><div><div></div>
<br></div></div></div></blockquote></div>