Dave Hart suggested I post the following event log information about leap
second behaviour on various Windows stratum-1 and stratum-2 PCs here..
___
Stratum-1 server PC Alta (Win-7/64 + Sure GPS) (runs 24 x 7)
LevelDate and Time
From: Dave Hart
Sent: Sunday, July 01, 2012 5:12 PM
To: David J Taylor
[]
As I mentioned on the pool list, I think there's a bug in the
application of the leap second to the local clock in recent ntpd.
Please check the event log on each of your Windows systems around the
event. If everything work
On Sun, Jul 1, 2012 at 09:24 UTC, David J Taylor wrote:
> - The Windows PCs fed from either Garmin GPS 18/x LVC or Sure Electronics
> GPS boards appear to have reset itself some 17..24 minutes after 00:00,
> suggesting they were using the GPS for the time (as well as the precise PPS
> edge), and th
My FreeBSD machines did fine, including the on connected to the Sure
Electronics board.
I think the Sure GPS board repeated the 59th second, from the looks of the NMEA
outout, but I need to check that more carefully. I will check and see if I saw
any
kind of reload later.
I took some other measu
For what it's worth, I saw no showstopper bugs with either my FreeBSD or
Windows systems.
- The FreeBSD 8.2 fed from the Garmin GPS 18 LVC behaved perfectly. ntpd
4.2.7p255
- The Windows PCs fed from either Garmin GPS 18/x LVC or Sure Electronics
GPS boards appear to have reset itself some
On 6/30/2012 17:09, A C wrote:
It appears that my system did not respond well to the leap second.
The GPS has not yet received the leap second notification via the
satellites (it is currently still reporting an offset of 15 seconds).
The leap second was inserted by ntpd according to the leap fil
