Re: [LEAPSECS] Greetings from an intercalary second

2017-01-01 Thread Daniel R. Tobias
On 1 Jan 2017 at 14:27, Clive D.W. Feather wrote: > Steve Summit said: > > But on the wire it was: > > > > Date: Sat, 31 Dec 2016 18:59:60 -0500 > > That's what mutt showed me (I'm running sendmail on my > own FreeBSD box). That's also what Pegasus Mail for Windows shows. -- == Dan ==

Re: [LEAPSECS] Happy Leap Second alarm

2017-01-01 Thread Steve Allen
On Sat 2016-12-31T16:13:20 -0800, Steve Allen hath writ: > We will reboot the telescope control computer before sunset, and > everything will be happy again. Which included a manual process that must be followed exactly, and was not due to low staffing and the holiday. Bad weather prevented

Re: [LEAPSECS] Leap seconds still broken

2017-01-01 Thread Warner Losh
les of failure, where 2 of the 4 setups got it wrong - > http://www.spinellis.gr/blog/20170101/ Looks like I need to go look into why the FreeBSD kernel code to see why it failed this time. I wonder who broke it this time. I've fixed it a co

Re: [LEAPSECS] Greetings from an intercalary second

2017-01-01 Thread John Hawkinson
Since no one has yet mentioned it: Steve Summit wrote on Sat, 31 Dec 2016 at 19:11:51 -0500 in <2016dec31.1911.scs.0...@eskimo.com>: > I should have said: readers who are able to view the raw Date: > line "on the wire". Any mail software which parses and > redisplays the

Re: [LEAPSECS] Leap seconds still broken

2017-01-01 Thread Tony Finch
Another example of software crashing when time seems to go backwards: https://blog.cloudflare.com/how-and-why-the-leap-second-affected-cloudflare-dns/ Tony. -- f.anthony.n.finch http://dotat.at/ - I xn-- zr8h punycode ___

Re: [LEAPSECS] alternative to smearing

2017-01-01 Thread John Sauter
I have updated my paper on avoiding the use of POSIX time_t for telling time, adding some example code and some recommendations for improving the Linux kernel.  The updated paper is at the same URL: I intend

Re: [LEAPSECS] Leap seconds still broken

2017-01-01 Thread Tony Finch
Ask Bjørn Hansen <a...@develooper.com> wrote: > > Meanwhile over in reality even the software that’s supposed to > keep track > of time basically still fails on leap seconds. More examples of failure, where 2 of the 4 setups got it wrong - http://www.spinellis.gr/blo

Re: [LEAPSECS] 2016 is not tied for second longest year ever

2017-01-01 Thread Tony Finch
Warner Losh wrote: > > There's also other year reckonings for other cultures that produce > very long results depending on what you tag as "a year" The Jewish calendar uses intercalary months, so a leap year can be 385 days.

Re: [LEAPSECS] Greetings from an intercalary second

2017-01-01 Thread Clive D.W. Feather
Steve Summit said: > But on the wire it was: > > Date: Sat, 31 Dec 2016 18:59:60 -0500 That's what mutt showed me (I'm running sendmail on my own FreeBSD box). -- Clive D.W. Feather | If you lie to the compiler, Email: cl...@davros.org | it will get its revenge. Web:

Re: [LEAPSECS] Leap seconds still broken

2017-01-01 Thread David Malone
Hi Ask, > Meanwhile over in reality even the software that’s supposed to > keep track of time basically still fails on leap seconds. Even some > national standard time servers got it wrong. > https://community.ntppool.org/t/leap-second-2017-status/59/ Do you have a record of how many