Leap Second Alert

[ronalddheld]

It is almost here. Those with the proper equipment might record the event and post it here?

[ronalddheld]

Net Tools
If anyone in the US gets this working before 8 pm ET, post it here.

[Hans Moleman]

Thanks for the reminder Ronald!

These were the NMEA sentences from my GPS around 235955.

Normally there would be only one 'GPRMC 000000' line. The leap second added the additional one.

The hazy part obscures my GPS coordinates. If you're curious about them PM me.

[ronalddheld]

From Time-nuts:

Message: 5
Date: Sat, 30 Jun 2012 19:05:53 -0500
From: Scott Newell <newell+timenuts@n5tnl.com>
To: time-nuts@febo.com
Subject: [time-nuts] ACTS leap second caught!
Message-ID: <mailman.107.1341101232.1867.time-nuts@febo.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed

National Institute of Standards and Technology
Telephone Time Service, Generator 1c
Enter the question mark character for HELP
D L
MJD YR MO DA HH MM SS ST S UT1 msADV <OTM>

56108 12-06-30 23:59:35 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:36 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:37 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:38 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:39 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:40 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:41 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:42 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:43 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:44 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:45 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:46 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:47 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:48 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:49 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:50 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:51 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:52 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:53 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:54 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:55 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:56 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:57 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:58 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:59 50 1 -.6 045.0 UTC(NIST) *
56108 12-06-30 23:59:60 50 1 -.6 045.0 UTC(NIST) *
56109 12-07-01 00:00:00 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:01 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:02 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:03 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:04 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:05 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:06 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:07 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:08 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:09 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:10 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:11 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:12 50 0 +.4 045.0 UTC(NIST) *
56109 12-07-01 00:00:13 50 0 +.4 045.0 UTC(NIST) *

[Phil_P]

My server automatically adjusted for it:

# cat /var/log/messages | grep leap
Jul 1 00:59:59 Quad kernel: Clock: inserting leap second 23:59:60 UTC

Unfortunately I wasn't around to witness it first hand though.

[scada]

How is this:

[harris498]

Thanks to all who recorded the event. Very interesting, and inconvienent when it comes to resetting my HAQs.

[webvan]

Thanks for the heads up, glad you posted that since I was initially concerned after checking my OQ with the video method and not finding it at -2 spy where I finally managed to set it! I'll have to add 1 second to my spreadsheet for my other HAQs

[The Naf]

Thanks a lot. Been visually inspecting my precisionist for a few weeks now and this woulda Definately have thrown me off...

[stanislav]

My GS SBGX065 was -1 s from last DST adjustment, now it is spot on.