Found a recording of the 7 pips on You Tube as witnessed at Bush House
(now vacated):
http://www.youtube.com/watch?v=FTnMLiOqNKk
And other You Tube leap second videos:
http://www.youtube.com/watch?v=1scvSm3Em3U
http://www.youtube.com/watch?v=xfhHPaZb8MI
http://www.youtube.com/watch?v=RyPZldmAAG
Peter:
Is my little blurb on GMT and the BBC (in http://gauss.gge.unb.ca/GMT.UT.and.the.RGO.html)
still more or less correct? Anything I should add/change? There are
a few statements in the article that I would like to tighten up and I
might as well get them all done at the same time.
-- Ri
Thanks, Peter. I had missed that.
-- Richard
On 11-Jul-12, at 8:38 AM, Peter Vince wrote:
Hi Richard,
Yes, BBC Radio 4 Long Wave on 198 KHz certainly did. David
Malone in Ireland grabbed the LF spectrum and sent a message to the
list at 13:25 (British Summer Time) on the 1st of July - his
Hi Richard,
Yes, BBC Radio 4 Long Wave on 198 KHz certainly did. David
Malone in Ireland grabbed the LF spectrum and sent a message to the
list at 13:25 (British Summer Time) on the 1st of July - his
spectrogram at
http://www.maths.tcd.ie/~dwmalone/time/leap2012/spectrogram.png
clearly shows
Peter:
Did any BBC radio station transmit the 7-pip Greenwich Time Signal for
the leap second? I did check the iPlayer repeats from BBC Radios 1
through 5 but it appears that these stations, at least via iPlayer,
didn't use it. Unlike for the 2008 leap second when Radio 5 made a big
deal a
On 11 July 2012 02:42, Michael Spacefalcon wrote:
> Of course. However, this issue would only exist if the external time
> input is an ASCII string or struct in HH:MM:SS format, and I have yet
> to see a system that uses such formats for time interchange. All
> systems that I'm familiar with us
Daniel R. Tobias wrote:
> Actually, from what I've seen and heard about this year's crop of
> bugs, server crashes, etc., relating to the leap second, the big
> problems come when the developers know and care just enough to be
> dangerous.
Yup.
> If you take the total dumbass approach to lea
Dan wrote:
> It's only when you actually attempt to get the system to account for
> the leap second immediately and precisely when it happens that you
> end up having to code in something convoluted that only runs every
> couple of years, with all the potential to screw it up and cause a
> majo
On 10 Jul 2012 at 8:38, Warner Losh wrote:
> You really don't understand the depth of the leap second issue in
> software. If it were that easy, it would have actually been
> solved. People just don't care, and that's the problem.
Actually, from what I've seen and heard about this year's crop
On Jul 10, 2012, at 11:17 AM, Rob Seaman wrote:
> Your message seems snarkier (more "cranky, irritable") than mine. You
> speculate on what I do or don't understand, and on what I am or am not doing.
> All of these are irrelevant. I'm a big fan of FreeBSD and PHK's MD5
> password hashing, bu
Warner,
Your message seems snarkier (more "cranky, irritable") than mine. You
speculate on what I do or don't understand, and on what I am or am not doing.
All of these are irrelevant. I'm a big fan of FreeBSD and PHK's MD5 password
hashing, but still disagree with his position on leap secon
On Jul 10, 2012, at 8:26 AM, Rob Seaman wrote:
> On Jul 10, 2012, at 7:09 AM, Warner Losh wrote:
>
>> On Jul 10, 2012, at 7:12 AM, Daniel R. Tobias wrote:
>>
>>> On 9 Jul 2012 at 14:31, Warner Losh wrote:
>>>
First, the current "right" database can't be updated in place:
you have to
On Jul 10, 2012, at 7:09 AM, Warner Losh wrote:
> On Jul 10, 2012, at 7:12 AM, Daniel R. Tobias wrote:
>
>> On 9 Jul 2012 at 14:31, Warner Losh wrote:
>>
>>> First, the current "right" database can't be updated in place:
>>> you have to restart.
>>
>> M$ Windows people are used to constantly ha
On Jul 10, 2012, at 7:12 AM, Daniel R. Tobias wrote:
> On 9 Jul 2012 at 14:31, Warner Losh wrote:
>
>> First, the current "right" database can't be updated in place:
>> you have to restart.
>
> M$ Windows people are used to constantly having to restart their
> systems at the most trivial updat
On 9 Jul 2012 at 14:31, Warner Losh wrote:
> First, the current "right" database can't be updated in place:
> you have to restart.
M$ Windows people are used to constantly having to restart their
systems at the most trivial updates... *Nix folks are spoiled!
--
== Dan ==
Dan's Mail Format Sit
On Jul 9, 2012, at 1:31 PM, Warner Losh wrote:
> On Jul 9, 2012, at 1:58 PM, Hal Murray wrote:
>
>> How often do systems need to get updated to track time zone changes?
>
> The ones that run on UTC? Never.
>
>> Has the US Congress stopped playing with DST rules? When was the last
>> change in
On Jul 9, 2012, at 1:58 PM, Hal Murray wrote:
>
>> (1) Push for a longer time horizon for leap second announcements. For
>> compute guys, the more lead time the better. 6 months is just too short to
>> meet deployment realities. 5 years would cover most bases, with 10 years
>> covering all bu
> (1) Push for a longer time horizon for leap second announcements. For
> compute guys, the more lead time the better. 6 months is just too short to
> meet deployment realities. 5 years would cover most bases, with 10 years
> covering all but a vanishingly small number. Even 2-3 years would he
18 matches
Mail list logo
