On Fri, Jun 29, 2012 at 5:33 PM, Kenyon Ralph <[email protected]> wrote:
> On 2012-06-29T15:01:21-0400, AlbyVA <[email protected]> wrote:
>> Being an EDT/EST snob, I had my cron job all set for 11:59p tonight to
>> record the leap second. But then reading an article today on the topic,
>>
>> I realized this isn't happening at midnight EDT -0400, but at UTC time
>> which will be 7:59p EDT.
>
> Yes, it's at 23:59:60 UTC: https://en.wikipedia.org/wiki/Leap_second
>
> You won't see anything on your computer clock though, since Unix time
> doesn't know anything about leap seconds.
> http://www.leapsecond.com/notes/leap-watch.htm
>
> --
> Kenyon Ralph
Just for grins I decided to check what I am getting this evening and
got the following results:
% ntpq
ntpq> associations
ind assid status conf reach auth condition last_event cnt
===========================================================
1 8687 961a yes yes none sys.peer sys_peer 1
2 8688 941a yes yes none candidate sys_peer 1
3 8689 943a yes yes none candidate sys_peer 3
4 8690 931a yes yes none outlyer sys_peer 1
5 8691 9144 yes yes none falsetick reachable 4
ntpq> rv 8687 leap
leap=00
ntpq> rv 8688 leap
leap=00
ntpq> rv 8689 leap
leap=00
ntpq> rv 8690 leap
leap=01
ntpq> rv 8691 leap
leap=00
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*ponderosa.piney 64.90.182.55 2 u 55 128 377 23.045 -2.047 4.579
+207.32.191.59 204.9.54.119 2 u 1 128 377 48.567 -3.686 0.899
+bindcat.fhsu.ed 132.163.4.102 2 u 49 128 377 66.332 -2.327 1.319
-vcxen02.bw.phl. 209.51.161.238 2 u 1 128 377 24.010 -7.198 1.802
x66.43.209.193 216.23.247.62 3 u 82 128 377 107.740 -73.680 127.936
My interpretation of this result is that only one of my peers is
advertising the leap second.
I find that interesting but not disturbing.
Bill W
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
