On Sep 25, 10:48 pm, [EMAIL PROTECTED] (Danny Mayer) wrote: > > Actually, there's no need for the batch file, w32tm has the > > "stripchart" functionality built-in: > > C:\>w32tm /stripchart /computer:1.us.pool.ntp.org /period:5 /dataonly > > Tracking 1.us.pool.ntp.org [69.16.152.68]. > > The current time is 9/24/2007 11:55:05 AM (local time).
> > This tool is just doing an actual ntp query every period, so it is > > probably not the most accurate measure of statistics, but it is > > something. This particular server is a Windows 2003 Server SP2 domain > > controller with a few tweaks to w32time. As you can see, it does > > fairly well in terms of offset, staying within 8 ms of zero typically. > > 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? Using the w32tm tool is analgous to using ntpdate to sanity-check ntpd. Evandro is having lots of trouble with ntpd on windows, even though w32time works fine. Obviously, you'd get more information from monitoring the server using ntpd peerstats and "server x.x.x.x noselect". You can, of course, run this tool against multiple ntp servers to see that your chosen server isn't crazy. -- RPM _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
