According to Poul-Henning Kamp: > It looks synchronized to me, it just looks like it hasn't swung in yet ?
The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not able to get any accurate data from the device whereas 4.0.90f does. I get lots of these in /var/log/messages and it doesn't sync at all. -=-=- Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:38 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:38 tara ntpd[7600]: PARSE receiver #0: FAILED TIMECODE: "-" (check receiver configuration / cableling) Mar 6 14:02:50 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:02:52 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits Mar 6 14:03:35 tara ntpd[7600]: PARSE receiver #0: no data from device within poll interval (check receiver / cableling) -=-=- Maybe it is a problem with 4.0.92c... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
