On Jun 30, 2012, at 18:15, leapsecs-requ...@leapsecond.com wrote:
>
> ... Linux!
>
> or at least some variants thereof:
>
> https://twitter.com/mikko/status/219176755481673729
>
> http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today
We have
Another place to look is the IMAP sort extension. Section 2.2 of
http://tools.ietf.org/html/rfc5256 says to treat invalid times as 00:00 which
might be triggered by a leap second. Also since mailbox order is the tiebreaker
(the sort must be stable) you can find out if your IMAP server treats xx:
AJust about all my servers and clients (FreeBSD, Windows, OSX) leapt as
hoped, but a Soekris 4501 FreeBSD 8.2 server running ntp 4.2.4p5 didn't
behave. From the ntpq -crv data I see that it did not reset the leap
bits, though the clock offsets are ok and the new tai value is there.
The system
It may be hard to sort out the leap second issues (my heart is palpitating)
from the massive storms and power outages in the eastern USA:
http://www.reuters.com/article/2012/06/30/usa-weather-storm-idUSL2E8HU2WN20120630
Rob
___
LEAPSECS maili
On 2012 Jun 30, at 17:02, Rob Seaman wrote:
> Netflix survived! Rosemary and Thyme are tracking down another body in the
> garden…
and our new telescope just emitted this heretofore unseen but entirely
expected gem of warning about the clock difference between
the motor controller cards in the W
Netflix survived! Rosemary and Thyme are tracking down another body in the
garden...
--
On Jun 30, 2012, at 4:59 PM, Rob Seaman wrote:
> It may be hard to sort out the leap second issues (my heart is palpitating)
> from the massive storms and power outages in the eastern USA:
>
>
> htt
According to RFC 5322 (and its predecessor RFC 2822), the Date: header
that I'm putting on this message is valid:
Date: Sun, 01 Jul 2012 00:59:60 +0100
I wonder how many MUAs will be unable to date-sort it. The header
syntax is specified rather loosely: the BNF allows "99:99:99" as a
tim
... Linux!
or at least some variants thereof:
https://twitter.com/mikko/status/219176755481673729
http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/I
By now Google is in the midst of their sinusoidal leap smear,
so they won't go down.
http://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html
The linux kernel hackers are pretty sure that they fixed the
multiprocessor leap second lockup that happened 3.5 years ago.
https://b
Thanks Pete,
French speaking clock is spot on. I'll see how they handle it..
space or pip?
Le 01/07/2012 00:12, Peter Vince a écrit :
Hi Mike,
I have just called the BT Speaking Clock (from a landline in
London) and it is exactly one second slow - looks like they have
applied the le
Hi Mike,
I have just called the BT Speaking Clock (from a landline in
London) and it is exactly one second slow - looks like they have
applied the leap-second already!
Peter Vince
On 30 June 2012 22:58, mike cook wrote:
> In preparation for leap second observation on various sources,
In preparation for leap second observation on various sources, I have
just called the UK speaking clock a couple of times and found that it
was 36 seconds slow. I would expect a little delay as I am calling on my
mobile from France, but not that much.
Is anyone in the UK seeing any unusual of
12 matches
Mail list logo
