Hello Dave, 1. NTP configuration:
server 127.127.20.0 mode 24 minpoll 4 maxpoll 4 fudge 127.127.20.0 flag1 1 fudge 127.127.20.0 flag2 0 fudge 127.127.20.0 flag3 1 driftfile /etc/ntp.drift statsdir /var/log/ntp/ logfile /var/log/ntp/ntp.log logconfig +all statistics loopstats peerstats clockstats filegen peerstats file peers type day link enable filegen loopstats file loops type day link enable filegen clockstats file clocks type day link enable --------------------------------------------------------------------- 2. NTP was restarted intentionally to reflect the problem. Assuming that once the time is set properly I wonder why NTP resets the system clock by 0.3 seconds when restarted. 3. To verify if the problem is due to the handling of different times (UTC & GPS), NMEA driver was modified to ignore ZDG messages. As per the configuration shown above only ZDA messages are being used. 4. I feel that this problem might be related to the usage PPSAPI common code, since it never occurs in the earlier versions of NTP using local PPSAPI. 5. I'll try with kernel PPS disabled and setting the appropriate fudge flags and let you know the behavior. Thanks & Kind Regards, _Venu _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
