Tricky situation. First of all you should remove LOCAL(0). It is not needed now and can only fool ntpd in many situations.
Next, i think that's because GPS_NMEA differs from ntp1.vniiftri.r. And I bet you didn't set GPS_NMEA or ntp1.vniiftri.r as "prefer" because none of them is used as supported clock for PPS. 2012/3/10 alex n <alexv...@gmail.com> > Hi All, > > I have following: > > > ============================================================================== > LOCAL(0) .CTB1. 1 l 39m 8 0 0.000 0.000 > 0.000 > ntp1.vniiftri.r .PPS. 1 u 10 16 377 223.489 > 37.761 7.349 > xGPS_NMEA(0) .NV24. 0 l 9 16 377 0.000 0.021 > 0.004 > oPPS(0) .PPS. 0 l 7 16 377 0.000 > 0.020 0.004 > > > GPS_NMEA is nmea driver with pps support. Why GPS is falseticker > though it has a same offset as PPS? > > Thanks, > Alexis. > _______________________________________________ > questions mailing list > questions@lists.ntp.org > http://lists.ntp.org/listinfo/questions > > _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
