text book example why Leapseconds are bad

2006-01-01 Thread Poul-Henning Kamp
http://lheawww.gsfc.nasa.gov/users/ebisawa/ASCAATTITUDE/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.

Re: went pretty dang smoothly at this end

2006-01-01 Thread Keith Winstein
On Sat, 31 Dec 2005, Steve Allen wrote: On Sat 2005-12-31T20:51:03 -0500, Keith Winstein hath writ: (b) Am I mistaken, or did WWV fail to correctly beep in the new year? We had two shortwave radios going, one on 10 MHz, one on 15 MHz, and with the two the ionosphere was pretty much tamed.

Re: went pretty dang smoothly at this end

2006-01-01 Thread David Harper
On Sat, 31 Dec 2005, Rob Seaman wrote: Was watching time.gov and leapsecond.com (the comparative clocks). Counted up to 23:59:60 (well, 16:59:60 in Tucson). The GPS-UTC incremented as did the TAI-UTC. The TV didn't melt down either. No obvious Airbuses plummeting from the sky. Life be

Re: went pretty dang smoothly at this end

2006-01-01 Thread Ed Davies
Keith Winstein wrote: Some minor glitches: (a) My Garmin 12XL GPS receiver (software version 4.53) did not register the leap second on its time display. It went from 58 to 59 to 00, and stayed one second ahead for the next few minutes until I rebooted it. Then it came up

Re: December 2005 leap second on MSF, Rugby, England

2006-01-01 Thread Joseph S. Myers
On Sun, 1 Jan 2006, David Malone wrote: I didn't have the facilities to record any phase information. I did try recording BBC Radio 4, but they transmitted Big Ben rather than pips ;-( Having found that problem with Radio 4 last leap second, I tried BBC World Service this time (having tested

Re: December 2005 leap second on MSF, Rugby, England

2006-01-01 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Joseph S. Myers [EMAIL PROTECTED] writes: : The Linux kernel (with NTP synchronisation) duly syslogged : : Dec 31 23:59:59 digraph kernel: Clock: inserting leap second 23:59:60 UTC : : and Markus's program showed a transition from 1136073600.005623 to :

Leap Second in GPS Receiver NMEA Log

2006-01-01 Thread Richard Langley
Here are the logged NMEA $GPZDA messages from a ublox Antaris SuperSense GPS receiver: $GPZDA,235955.00,31,12,2005,00,00*6D $GPZDA,235956.00,31,12,2005,00,00*6E $GPZDA,235957.00,31,12,2005,00,00*6F $GPZDA,235958.00,31,12,2005,00,00*60 $GPZDA,235959.00,31,12,2005,00,00*61

CDMA glitches, and TAI over NTP

2006-01-01 Thread Neal McBurnett
There is an interesting thread at http://groups.google.com/group/comp.protocols.time.ntp/browse_thread/thread/30a0f68a30f83f1e/ in which Bruce Penrod notes that some of their customers didn't configuree their CDMA cell phone basestations right: We are pleased to announce that our GPS NTP

TAI, NTP and IETF; IEEE 1588

2006-01-01 Thread Neal McBurnett
I hadn't run across NIST's leap seconds table before: ftp://time.nist.gov/pub/leap-seconds.list I'm finally beginning to catch up on NTP developments over the last several years, and find that current xntpd code can use that table, and transport leap second tables around using an autokey

Re: went pretty dang smoothly at this end

2006-01-01 Thread Tim Shepard
The first officer gave us a countdown to midnight in London, and I'm happy to report that the plane failed to fall out of the sky, explode, or otherwise deviate from its course at 23:59:60. Did his countdown reach zero at 23:59:60 31-December-2005 UTC or at 00:00:00 1-January-2006 UTC ?

NTP behavior in Australia

2006-01-01 Thread Steve Allen
Here is one indication of NTP response to the presence of low stratum servers which did not behave well. http://members.iinet.net.au/~nathanael/ntpd/leap-second.html -- Steve Allen [EMAIL PROTECTED]WGS-84 (GPS) UCO/Lick ObservatoryNatural Sciences II, Room