> what i mean is... why would it jump from 0 ns to 1000 ns and back?
What hardware and OS are you running on? Does it take 1 uSec to read the
clock?
ntpd keeps track of the resolution of the system clock. It's measured by how
long it takes to read the clock rather than observing low bits in t
On Mon, Oct 17, 2011 at 6:34 PM, Bill Dailey wrote:
> what i mean is... why would it jump from 0 ns to 1000 ns and back?
>
Looks like .01 is the least significant digit. Those three trailing
zeros are just tacked on. So the jump to "1000" and back is really a jump
to "1" and back, likely
what i mean is... why would it jump from 0 ns to 1000 ns and back?
On Mon, Oct 17, 2011 at 8:04 PM, Bill Dailey wrote:
> thanks, what am i seeing here?
>
>
> 55852 3520.152 -0.01000 -29.727 0.01083 0.000168 4
> 55852 3536.152 0.0 -29.727 0.01068 0.000158 4
> 55852 3552.152 0.
> thanks, what am i seeing here?
> 55852 3520.152 -0.01000 -29.727 0.01083 0.000168 4
> 55852 3536.152 0.0 -29.727 0.01068 0.000158 4
...
The info is in monopt.html
The details sometimes depend upon which version of ntpd you are using so it's
best to use the documentation th
thanks, what am i seeing here?
55852 3520.152 -0.01000 -29.727 0.01083 0.000168 4
55852 3536.152 0.0 -29.727 0.01068 0.000158 4
55852 3552.152 0.0 -29.727 0.01054 0.000147 4
55852 3568.152 -0.02000 -29.728 0.01074 0.000221 4
55852 3584.152 0.0 -29.7
Le 17/10/2011 16:55, Bill Dailey a écrit :
I need an NTP guru for a couple NTP questions. I have my Fury GPSDO hooked
up to a linux (ubuntu) computer have offset in the "time-nuts" category
(less than a microsecond) with pps. I am wondering where to go from here so
I can actually quantify the p
I need an NTP guru for a couple NTP questions. I have my Fury GPSDO hooked
up to a linux (ubuntu) computer have offset in the "time-nuts" category
(less than a microsecond) with pps. I am wondering where to go from here so
I can actually quantify the precision (it is below the standard minimum fo
