Hi Pearly, based on your suggestion on the use of ntpq, I indeed ran those commands and the offset does indeed say about 26ms, see here:
associd=0 status=0418 leap_none, sync_uhf_radio, 1 event, no_sys_peer, version="ntpd 4.2.8p4@1.3265 Mon May 23 20:45:07 UTC 2016 (1)", , leap=00, stratum=1, precision=-15, rootdelay=0.000, rootdisp=26.313, refid=csac, reftime=daf1adb7.a5581391 Thu, May 26 2016 17:15:35.645, clock=daf1adbd.54fb354f Thu, May 26 2016 17:15:41.331, peer=6499, tc=4, mintc=3, offset=25.970500, frequency=500.000, sys_jitter=0.000000, clk_jitter=1.029, clk_wander=12.000 I shall have to see if my ntp build process was flawed. Our deployment target is a legacy Linux 2.6.10 system on Arm, and we have a fairly dated cross compiler toolchain. So getting ntp to cross-compile at all took a bit of effort, my exact sequence was this: $ mkdir arm-linux $ cd arm-linux $ ../configure --host=arm-linux --disable-GPSD --with-yielding-select $ make Perhaps those extra configure options, without which the build failed, introduce some offset of 26ms ?? I'll re-run ntpd on our target arm board under strace, and see it is using e.g. some drift file I was unaware of. Thanks again for your help and suggestions Stuart _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
