Paul writes: > On Wed, Jan 21, 2015 at 10:46 PM, Harlan Stenn <st...@ntp.org> wrote: > > > Right, so if you don't want that use sntp instead. > > Are these numbers consistent? If ntpdate is reporting seconds and sntp is > reporting milliseconds then it an order of magnitude difference. Otherwise > it's several orders of magnitude. > > server 192.168.0.244, stratum 1, offset -0.000009, delay 0.02571 > 22 Jan 10:46:13 ntpdate[31506]: adjust time server 192.168.0.244 offset > -0.000009 sec > > sntp 4.2.8p1-beta5@1.3265-o Tue Jan 20 04:48:55 UTC 2015 (2) > 2015-01-22 10:46:13.241424 (+0500) -0.00129 +/- 0.001866 ntpa 192.168.0.244 > s1
Please dig in to this. They are both reporting seconds. Note that sntp will give you the error bounds as well. And at this level on a Unix box, a millisecond is not bad for a one-shot time check. You can crank the debug levels to see the packet timestamps. H _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
