Jed Clear wrote: > David J Taylor wrote: >> No, it seemed that the sync still worked OK. I saw the same 0x03 >> errors on the FreeBSD system before I rebuilt the kernel to have the >> PPS_SYNC option. Since then, there's no console on that system, so >> I might still be getting the errors! [FreeBSD folk - what file >> should I "cat"?] > > /var/log/ntpd > /var/log/messages > [exec, not cat] dmesg [although these should be captured in > /var/log/messages] > > I'm running 4.11R, so YMMV. > > -Jed
Thanks, Jed. Cat rather than exec did actually do the job (even if there's a better way). Here is a selection of the results: Feb 3 07:53:11 pixie ntpd[346]: clock GPS_NMEA(1) event 'clk_fault' (0x03) Feb 3 07:54:08 pixie ntpd[346]: pps sync disabled Feb 3 07:54:14 pixie ntpd[346]: clock GPS_NMEA(1) event 'clk_fault' (0x03) Feb 3 07:55:19 pixie ntpd[346]: clock GPS_NMEA(1) event 'clk_fault' (0x03) Feb 3 07:58:22 pixie ntpd[346]: pps sync disabled Feb 3 08:03:54 pixie ntpd[346]: kernel time sync disabled 2307 Feb 3 08:04:51 pixie ntpd[346]: pps sync disabled Feb 3 08:04:59 pixie ntpd[346]: kernel time sync enabled 2107 Feb 3 10:18:37 pixie ntpd[346]: kernel time sync disabled 2307 Feb 3 10:19:34 pixie ntpd[346]: pps sync disabled Feb 3 10:19:43 pixie ntpd[346]: kernel time sync enabled 2107 Feb 3 10:46:34 pixie ntpd[346]: clock GPS_NMEA(1) event 'clk_fault' (0x03) Feb 3 10:47:31 pixie ntpd[346]: pps sync disabled Feb 3 10:48:44 pixie ntpd[346]: clock GPS_NMEA(1) event 'clk_fault' (0x03) Feb 3 10:49:38 pixie ntpd[346]: pps sync disabled Feb 3 11:23:18 pixie ntpd[346]: kernel time sync disabled 2307 Feb 3 11:24:15 pixie ntpd[346]: pps sync disabled Feb 3 11:24:21 pixie ntpd[346]: kernel time sync enabled 2107 Feb 3 11:30:46 pixie ntpd[346]: kernel time sync disabled 2307 Feb 3 11:31:42 pixie ntpd[346]: pps sync disabled Feb 3 11:31:49 pixie ntpd[346]: kernel time sync enabled 2107 Have to hope that doesn't wrap too badly! So I'm getting a mixture of the 2307/2107 fault pairs (I believe this is fixed in a more recent ntpd), and the clk_fault (0x03). I don't know what to do about the clk_fault. Cheers, David _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
