On Thu, Feb 9, 2012 at 12:19, Dave Hart wrote:
> ntpdc uses binary structures on the wire, and assumes implicitly all
> systems have identical binary representations. That works fine for
> integers, apparently not so well for floating-point.
This is mistaken on my part -- all the data involved i
On Wed, Feb 8, 2012 at 19:59, David J Taylor
wrote:
> Running on my Windows PC (ntpd 4.2.7p241) I get:
>
> C:\>ntpdc -c kerninfo pixie
> pll offset: 0.001216 s
> pll frequency: 27.793 ppm
> maximum error: 0.005504 s
> estimated error: 2e-006 s
> status: 2
On Thu, Feb 9, 2012 at 06:03, David J Taylor
wrote:
> This is the result
>
> C:\>ntpq -c kerninfo pixie
> ***A request variable unknown to the server
Right, this is expected. Newer ntpq commands added to replace ntpdc
equivalents usually rely on newly-introduced system variables in ntpd,
so
On 2012-02-08T19:59:49-, David J Taylor
wrote:
Running on my Windows PC (ntpd 4.2.7p241) I get:
C:\>ntpdc -c kerninfo pixie
[...]
Whereas logged into the FreeBSD 8.0 system (ntpd 4.2.4p5) I see:
pixie-ii# ntpdc -c kerninfo
Not only do the numbers look different, but the 2107 status isn'
On 2012-02-08T19:59:49-, David J Taylor
wrote:
> Running on my Windows PC (ntpd 4.2.7p241) I get:
>
> C:\>ntpdc -c kerninfo pixie
[...]
> Whereas logged into the FreeBSD 8.0 system (ntpd 4.2.4p5) I see:
>
> pixie-ii# ntpdc -c kerninfo
>
> Not only do the numbers look different, but the 210
Running on my Windows PC (ntpd 4.2.7p241) I get:
C:\>ntpdc -c kerninfo pixie
pll offset: 0.001216 s
pll frequency:27.793 ppm
maximum error:0.005504 s
estimated error: 2e-006 s
status: 2107
pll time constant:4
precision:1e-006 s
frequenc
