From: peter@rulingia.com (Peter Jeremy)
Subject: [TUHS] Leap Second
Date: Thu, 29 Dec 2016 11:21:05 +1100 [thread overview]
Message-ID: <20161229002105.GB94858@server.rulingia.com> (raw)
In-Reply-To: <alpine.BSF.2.20.1612291058070.43538@aneurin.horsfall.org>
On 2016-Dec-29 10:59:32 +1100, Dave Horsfall <dave at horsfall.org> wrote:
>(Yes, a repeat, but this momentous event only happens every few years.)
Actually, they've been more frequent of late.
>The International Earth Rotation Service has announced that there will be
>a Leap Second inserted at 23:59:59 UTC on the 31st December, due to the
>earth slowly slowing down. It's fun to listen to see how the time beeps
>handle it; will your GPS clock display 23:59:60, or will it go nuts
>(because the programmer was an idiot)?
Google chose an alternative approach to avoiding the 23:59:60 issue and will
smear the upcoming leap second across the period 2016-12-31 14:00:00 UTC
through 2017-01-01 10:00:00 UTC (see https://developers.google.com/time/smear).
Of course, this means that mixing time.google.com with normal NTP servers
will have "interesting" effects.
--
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20161229/c8d492e6/attachment.sig>
next prev parent reply other threads:[~2016-12-29 0:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 23:59 Dave Horsfall
2016-12-29 0:21 ` Peter Jeremy [this message]
2017-01-03 10:44 ` sds
2017-01-03 15:06 ` Tony Finch
2017-01-03 15:29 ` Joerg Schilling
2017-01-04 13:32 ` Steffen Nurpmeso
2017-01-04 23:13 ` Warner Losh
2017-01-05 14:29 ` Steffen Nurpmeso
2017-01-04 15:54 ` sds
-- strict thread matches above, loose matches on Subject: below --
2016-12-23 23:08 Dave Horsfall
2016-12-23 23:19 ` Michael Kjörling
2016-12-24 1:33 ` Charles Anthony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161229002105.GB94858@server.rulingia.com \
--to=peter@rulingia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).