From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] Leap Second
Date: Wed, 04 Jan 2017 14:32:02 +0100 [thread overview]
Message-ID: <20170104133202.VIWUz5j-a%steffen@sdaoden.eu> (raw)
In-Reply-To: <586bc353.tOFm/S0IGecYYlh6%schily@schily.net>
schily at schily.net (Joerg Schilling) wrote:
|Tony Finch <dot at dotat.at> wrote:
|> sds <stephen.strowes at gmail.com> wrote:
|>> Important question: did anybody have an "exciting" new year because \
|>> of a leap
|>> second bug?
|>
|> I've been collecting failure reports on the LEAPSECS list
|
|https://blog.cloudflare.com/how-and-why-the-leap-second-affected-cloudflare\
|-dns/
|
|"go" seems to have a related bug.
|
|BTW: The POSIX standard intentionally does not include leap seconds \
|in the UNIX
|time interface as it seems that this would cause more problems than \
|it claims
|to fix.
I think it is a problem, or better a gap, a void, with the current
standard that software has no option to become informed of the
event of a leap second for one, but further more that CLOCK_TAI is
not available. I think it would make things easier if software
which wants just that can get it, e.g., for periodic timer events
etc. This is surely not a healing given that most timestamps etc.
are based on UTC, but i think the severity of the problems could
possibly be lowered. Especially now that multi-hour smears seem
to become used by big companies it seems to be important to have
a correct clock available. This is in fact something i don't
really understand, at _that_ level that is to say. If, e.g.,
Google and Bloomberg both would have stated instead that they
slew the leap second, then only a single second would have been
affected, instead of multiple hours.
--steffen
next prev parent reply other threads:[~2017-01-04 13:32 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
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 [this message]
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=20170104133202.VIWUz5j-a%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
/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).