Particularly noticeable in the GPS-synced PC Pixie, because of the accuracy it Transition, as normally the temperature step at 06:00 in the morning and gradualĬool-down late at night causes a change in the offset which is Port for getting the code right! I left the heating on over the The analog clock on my main PC took two seconds to go between 00:00:00Īnd 00:00:01, so my thanks to the person who wrote that part of the Windows NTP As you can see, there was no disruption at the transition Dec 31 - JanĠ1. Here is a screen shot showing Decemberģ1 and January 01. Information 01:00:00 NTPē None Leap second announcement disarmedīy contrast with earlier events, the leap-second at the end ofĢ008 went of without a hitch. Warning 01:24:33 NTPĒ None clock would have gone backward 1 times, max 1000612.1 usec Peerstats, loopstats and event log entries for GPS-synced PC Alta (338 KB ZipĮvent log entries for PC Alta Levelĝate and Time SourceĞvent ID Task Category PCs Hydra, Molde, Narvik, Torvik and Ystad on the graphs, all running ntpd 4.2.7p285. LAN/WAN synced Windows PCs saw no glitch.PCs Alta, Bacchus, Feenix and Stamsund, running ntpd 4.2.7p285. Perhaps it would have been better had they not believed the GPS serial time, but that coming from other servers? The reset resulted in a further period of about an hour until full accuracy was restored. Refclock Windows PCs fed from either Garmin GPS 18/x LVC or Sure Electronics GPS boards appear to have reset some 17.24 minutes after 00:00, suggesting they were using the GPS for the time (as well as the precise edge), and the GPS devices took some time to reflect the leap-second in their serial outputs.FreeBSD 8.2 PC fed from the Garmin GPS 18 LVC behaved perfectly.Systems, although many Linux bugs were reported. I saw no showstopper bugs with either my FreeBSD or Windows
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |