Martin Burnicki writes: > 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.
When I have more time I'll look at how 'system' is being set - that *should* be the '$host' CPU-VENDOR-OS value. If that variable is too inconsistent, I'm game to add the 'host-cvo' and 'build-cvo' values (or host_cvo and build_cvo, if those names would be better). If cvo_host and cvo_build would be better, that's fine too. H _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
