I'm doing more configuration tests to test ATOM against other
configuration options and have turned on flag3 to enable use of the
kernel for PPS. Previously it was disabled and, without a preferred
peer, ATOM was never activated. With a preferred peer, it would be
activated but all clocks were clamped at 64 s polling intervals.
However, if I enable flag3, ATOM does activate without a preferred peer
but it's always labeled as a falseticker, the system claims it isn't
using PPS (the reported stratum of my system is 3 not 1) and I'm not
really sure why (it also lets the other servers increase their polling
intervals).
The configuration:
logconfig -syncstatus
logconfig =sysall +syncall +peerall +clockall
logfile /var/log/ntp/ntpd.log
pidfile /var/run/ntpd.pid
driftfile /var/db/ntpd.drift
leapfile /etc/leap-seconds.list
statistics loopstats clockstats sysstats
statsdir /var/log/ntp/
filegen peerstats file peers type day link enable
filegen loopstats file loops type day link enable
filegen clockstats file clockstats type day link enable
filegen sysstats file sysstats type day link enable
tos mindist 1.0
server 0.us.pool.ntp.org iburst
server 1.us.pool.ntp.org iburst
server 0.north-america.pool.ntp.org iburst
server ntp1.gatech.edu iburst
server rolex.usg.edu iburst
server 127.127.22.0 minpoll 4
fudge 127.127.22.0 time1 -0.000 flag2 1 flag3 1 flag4 1 refid PPS
server 127.127.28.0 minpoll 6
fudge 127.127.28.0 stratum 4 time1 -0.6 flag4 1 refid GPSD
And the billboard:
remote refid st t when poll reach delay offset
jitter
==============================================================================
x127.127.22.0 .PPS. 0 l 1 16 377 0.000 0.007
0.122
-127.127.28.0 .GPSD. 4 l 32 64 377 0.000 -9.611
4.715
-208.53.158.34 204.9.54.119 2 u 168 1024 377 86.920 6.524
0.214
*64.5.0.130 128.138.141.172 2 u 152 1024 377 69.132 5.423
1.879
+69.65.40.29 209.51.161.238 2 u 20 1024 377 76.177 4.389
0.651
+130.207.165.28 130.207.244.240 2 u 251 1024 377 80.551 5.165
5.054
-131.144.4.10 130.207.244.240 2 u 57 1024 377 98.164 -2.061
0.502
and -c rv:
# ntpq -c rv
assID=0 status=061d leap_none, sync_ntp, 1 event, event_13,
version="ntpd [email protected] Sun Feb 26 20:36:27 UTC 2012 (2)",
processor="sparc", system="NetBSD/5.1", leap=00, stratum=3,
precision=-13, rootdelay=110.865, rootdisp=1002.880, refid=64.5.0.130,
reftime=d31d0775.cf8f9b33 Wed, Mar 28 2012 3:43:49.810,
clock=d31d0835.f6efcd5f Wed, Mar 28 2012 3:47:01.964, peer=45635,
tc=10, mintc=3, offset=4.996, frequency=-77.202, sys_jitter=0.747,
clk_jitter=0.011, clk_wander=0.075, tai=34, leapsec=201207010000,
expire=201212280000
If I turn off flag3 and set up a preferred peer, the system does use
ATOM and reports that in ntpq -c rv (plus the tally code is 'o').
This is version 4.2.7p259.
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
