David, To verify your assumption, see rackety.udel.edu or pogo.udle.edu. The Spectracom driver shows leap 01, as does the PPS driver. However, in order to comply with NTPv3, the server itself does not show leap 01, even if other upstream servers show 01. The proof will be available only on the day of the leap.
When a leap event is ccheduled, the EVNT_ARMED event/protostats/syslog trap is raised. When it is descheduled, like when the upstream leap bits are set and then reset, the EVNT_DISARMED event is raised. You should see that at the appropriate places. Dave David J Taylor wrote: >Unruh wrote: > > >>"David J Taylor" >> >> >[] > > >>>In view of the popularity of the GPS18-LVC it's a pity that the >>>driver support for the leap second isn't better, but I appreciate >>>that being able to test once every few years doesn't make things any >>>easier! >>> >>> >>As far as I can see, the GPS18-LVC unit does NOT warn of leapseconds. >>There is absolutely nothing the driver can do if the information is >>not supplied by >>the GPS unit. >> >> > >Yes, that was poorly worded - I meant "shouldn't NTP note the leap-second >flags from the other Internet upstream servers, and base its whole second >values on those sources during a leap-second update, using just the PPS >part of the GPS signal?" The would appear to apply to any GPS source >which is PPS + NMEA.... > >David > >_______________________________________________ >questions mailing list >[email protected] >https://lists.ntp.org/mailman/listinfo/questions > > _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
