| Re: [chrony-users] ntpd refclock drivers with chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
Miroslav Lichvar wrote:
Thanks. This is helpful. The PARSE driver is different from the other drivers in that it uses a "direct" input. It seems there were at least two bugs in ntp-refclock related to that. Could you please pull from git and try again?
Ok now it is better!
2017-11-29T19:55:00.221331+01:00 linux ntp-refclock[6883]: PARSE receiver #0: STATE CHANGE: -> TIME CODE; (LEAP INDICATION; CALLBIT)
2017-11-29T19:55:00.221586+01:00 linux ntp-refclock[6883]: PARSE receiver #0: SYNCHRONIZED
chronyc sources
210 Number of sources = 9
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#* PPS 0 4 377 14 -122ns[ -234ns] +/- 215ns
#? DCF 0 6 1 9 -421us[ -421us] +/- 43ns
(and a couple of network sources)
Rob
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.