[ntp:questions] NTP Third party client on Windows OS ?

Evandro Menezes evandro at mailinator.com
Wed Sep 26 17:11:26 UTC 2007


On Sep 25, 10:48 pm, ma... at ntp.isc.org (Danny Mayer) wrote:

> Huh? What accuracy? All it's telling you is how close the local clock is
> to the expected clock. It tells you nothing about how accurate it is. If
> the remote clock is off by 5 minutes then so will your clock be, but it
> will track that inaccuracy. Is that what you want?

That's true, but W32TM is the only tool that works for both W32TIME
and NTP.

Besides, I used this W32TM trick when both NTP and W32TIME were
running, so it woould be as bad for both time synchronization
facilities.  And the results by W32TM for NTP confirm its peerstats,
so it's not that far off.

The fact remains that W32TIME is doing a "better" (your definition may
vary) job than NTP to keep my system time in "lock-step" (your
definition may vary) with a reference.

I don't mean by this that W32TIME has better algorithms than NTP.  I
wouldn't be able to state that.  But I suspect that Microsoft knows
its kernel better, if not using a back-door that only they know about,
as it's happened in the past, and that for a lousy clock as the one in
my system it manages to do well.

Besides, I think that NTP is proven to do a good jon on Windows too.
Hey, it does a fine job on my personal laptop! ;-)

Thanks.




More information about the questions mailing list