On 3/27/2012 22:07, Dave Hart wrote:
On Wed, Mar 28, 2012 at 03:52, A C<agcarver+...@acarver.net> wrote:
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
Please try:
fgrep kcbind /var/log/ntp/ntpd.log
I suspect you will see that when you've used flag3 1, ntpd has
reported time_pps_kcbind failing. I do see a potential bug in that
code, though. If you don't get any hits from the fgrep, try removing
line 1259 from ntp_refclock.c:
if (errno != EOPNOTSUPP) {
and its matching closing brace on line 1265:
}
Then recompile ntpd and see if it then reports time_pps_kcbind failure
with flag3 1.
No hits from fgrep but quoted below is the part of the log from the
point where ntpd was restarted earlier today (note kern PPS enabled).
I will recompile with the modification.
27 Mar 19:47:54 ntpd[22142]: 0.0.0.0 c01e 0e TAI 35 leap 201207010000
expire 201212280000
27 Mar 19:47:55 ntpd[22142]: PPS(0) 8011 81 mobilize assoc 45632
27 Mar 19:47:55 ntpd[22142]: SHM(0) 8011 81 mobilize assoc 45633
27 Mar 19:47:56 ntpd[22142]: 0.0.0.0 c01d 0d kern kernel time sync enabled
27 Mar 19:47:56 ntpd[22142]: 0.0.0.0 c012 02 freq_set kernel -77.753 PPM
27 Mar 19:47:56 ntpd[22142]: 0.0.0.0 c016 06 restart
27 Mar 19:47:56 ntpd[22142]: DNS 0.us.pool.ntp.org -> 208.53.158.34
27 Mar 19:47:56 ntpd[22142]: 208.53.158.34 8011 81 mobilize assoc 45634
27 Mar 19:47:56 ntpd[22142]: DNS 1.us.pool.ntp.org -> 64.5.0.130
27 Mar 19:47:56 ntpd[22142]: 64.5.0.130 8011 81 mobilize assoc 45635
27 Mar 19:47:56 ntpd[22142]: DNS 0.north-america.pool.ntp.org -> 69.65.40.29
27 Mar 19:47:56 ntpd[22142]: 69.65.40.29 8011 81 mobilize assoc 45636
27 Mar 19:47:56 ntpd[22142]: DNS ntp1.gatech.edu -> 130.207.165.28
27 Mar 19:47:56 ntpd[22142]: 130.207.165.28 8011 81 mobilize assoc 45637
27 Mar 19:47:57 ntpd[22142]: 64.5.0.130 8024 84 reachable
27 Mar 19:47:57 ntpd[22142]: 208.53.158.34 8024 84 reachable
27 Mar 19:47:57 ntpd[22142]: SHM(0) 8024 84 reachable
27 Mar 19:47:57 ntpd[22142]: SHM(0) 903a 8a sys_peer
27 Mar 19:47:57 ntpd[22142]: DNS rolex.usg.edu -> 131.144.4.10
27 Mar 19:47:57 ntpd[22142]: 131.144.4.10 8011 81 mobilize assoc 45638
27 Mar 19:47:58 ntpd[22142]: 0.0.0.0 c415 05 clock_sync
27 Mar 19:47:58 ntpd[22142]: 0.0.0.0 0419 09 leap_armed
27 Mar 19:47:58 ntpd[22142]: 69.65.40.29 8024 84 reachable
27 Mar 19:48:00 ntpd[22142]: 131.144.4.10 8024 84 reachable
27 Mar 19:48:01 ntpd[22142]: 130.207.165.28 8024 84 reachable
27 Mar 19:48:12 ntpd[22142]: 69.65.40.29 903a 8a sys_peer
27 Mar 19:48:12 ntpd[22142]: PPS(0) 8024 84 reachable
27 Mar 19:53:17 ntpd[22142]: 131.144.4.10 943a 8a sys_peer
27 Mar 19:53:17 ntpd[22142]: 0.0.0.0 061d 0d kern PPS enabled
27 Mar 19:55:08 ntpd[22142]: 64.5.0.130 933a 8a sys_peer
27 Mar 20:02:53 ntpd[22142]: 69.65.40.29 941a 8a sys_peer
27 Mar 20:16:01 ntpd[22142]: 130.207.165.28 943a 8a sys_peer
27 Mar 20:22:31 ntpd[22142]: SHM(0) 934b 8b clock_event clk_no_reply
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
