David Taylor wrote:
On 17/12/2014 08:52, Martin Burnicki wrote:
[]
This is just a subset of the information you get from "ntpq -c rv", e.g.:
associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync,
version="ntpd 4.2.6p5@1.2349-o Jul 30 11:55:08 (UTC+02:00) 2012 (2)",
processor="x86", system="Windows", leap=00, stratum=2, precision=-10,
rootdelay=0.015, rootdisp=4.447, refid=172.16.3.9,
reftime=d83bc128.df638c2d Wed, Dec 17 2014 9:45:28.872,
clock=d83bc157.26a94acd Wed, Dec 17 2014 9:46:15.151, peer=29231,
tc=6, mintc=3, offset=0.171, frequency=500.000, sys_jitter=0.000,
clk_jitter=0.985, clk_wander=0.003
telling on which system ntpd is running, *not* on which system it has
been built.
Martin
That fails here, then, as I'm running on 64-bit Windows and seeing x86
as the processor.
Agreed. Maybe this should better be labelled "target architecture" or
similar instead of "processor". ;-)
Windows exports an environment variable (don't know if ntpd uses this
environment setting, though), and on a 32 bit version of Windows 7 there
is, for example:
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 107 Stepping 1, AuthenticAMD
even though running on a 64 bit capable hardware. A 64 bit Windows 7 has:
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
> Oh, and NTP was built on a 64-bit system as a 32-bit
application! <G> Yes, I understand why this is....
;-)
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
