[EMAIL PROTECTED] writes: [...] > Hi Ulrich - it does change... Output attached. > ntptime > ntp_gettime() returns code 0 (OK) > time c7d2d4df.554f0000 Mon, Mar 27 2006 13:17:19.333, (.333237), > maximum error 993 us, estimated error 1 us > ntp_adjtime() returns code 0 (OK) > modes 0x0 (), > offset 1.000 us, frequency -158.380 ppm, interval 4 s, > maximum error 993 us, estimated error 1 us, > status 0x1 (PLL), > time constant 0, precision 1.000 us, tolerance 496 ppm, > pps frequency -159.438 ppm, stability 0.000 ppm, jitter 0.000 us, > intervals 0, jitter exceeded 0, stability exceeded 0, errors 0.
Your "intervals" are "0", so no PPS is actually coming in. Also, your STA_NANO is not set, so I guess you are running the wrong kernel or ntpd. > from ntpq -p > *GPS_ONCORE(0) .GPS. 0 l 1 16 377 0.000 0.001 > 0.001 > > So is something broken with the PPS freq changing? With a remote > server connected to 4st 1 servers, one of which is mine, it often picks > mine to update from (*) - (depending on load being put on the dsl > line.) > > Thanks, > Ryan > > > Regards, > > Ulrich _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
