On Mon, 2 Jul 2012 11:32:45 -0400
Michael Mol wrote:
> On Mon, Jul 2, 2012 at 9:09 AM, Alan McKinnon
> wrote:
> > On Mon, 2 Jul 2012 11:35:50 +0700
> > Pandu Poluan wrote:
> >
> >> Just wondering... did Saturday's "Leap Second" bit your
> >> infrastructure?
> >
> > Nope, that a murmur, not a pe
On Mon, 2 Jul 2012 11:32:45 -0400
Michael Mol wrote:
>
> Just wondering... did Saturday's "Leap Second" bit your
> infrastructure?
>
Being just a user of Linux desktop applications the leap-second issue
has no relevance to my activities.
However, I have read in several places that any potenti
On Mon, Jul 2, 2012 at 9:09 AM, Alan McKinnon wrote:
> On Mon, 2 Jul 2012 11:35:50 +0700
> Pandu Poluan wrote:
>
>> Just wondering... did Saturday's "Leap Second" bit your
>> infrastructure?
>
> Nope, that a murmur, not a peep, barely even a log entry anywhere. And
> no whinging customers (surpri
On Mon, 2 Jul 2012 11:35:50 +0700
Pandu Poluan wrote:
> Just wondering... did Saturday's "Leap Second" bit your
> infrastructure?
Nope, that a murmur, not a peep, barely even a log entry anywhere. And
no whinging customers (surprisingly!) Our ntp servers just synced with
the upstream stratum and
On Mon, Jul 2, 2012 at 12:35 AM, Pandu Poluan wrote:
> Just wondering... did Saturday's "Leap Second" bit your infrastructure?
>
> Did you do something special (like Google did) to prevent chaos?
>
> 'Leap Second' Bug Wreaks Havoc Across Web | Wired Enterprise | Wired.com
> http://m.wired.com/wire
On Mon, Jul 2, 2012 at 12:35 AM, Pandu Poluan wrote:
> Just wondering... did Saturday's "Leap Second" bit your infrastructure?
>
> Did you do something special (like Google did) to prevent chaos?
>
> 'Leap Second' Bug Wreaks Havoc Across Web | Wired Enterprise | Wired.com
> http://m.wired.com/wire
Just wondering... did Saturday's "Leap Second" bit your infrastructure?
Did you do something special (like Google did) to prevent chaos?
'Leap Second' Bug Wreaks Havoc Across Web | Wired Enterprise | Wired.com
http://m.wired.com/wiredenterprise/2012/07/leap-second-bug-wreaks-havoc-with-java-linux
There is a good article on current thinking in Washington Post :
http://www.washingtonpost.com/wp-dyn/content/article/2005/12/25/AR2005122500496_pf.html
It doesn't mention NTP, but that's implicit in the anti-leap position.
--
,,===
On Sun, 25 Dec 2005 06:59:20 -0500
Philip Webb <[EMAIL PROTECTED]> wrote:
> The details are in Appx E : it seems a warning bit is set manually
> by the operator of the primary time server during the previous day
Seems like I should have looked more carefully.
> & one supposes -- hopes (smile) --
051225 Ian Hastie wrote:
> 24 Dec 2005 Philip Webb <[EMAIL PROTECTED]> wrote:
>> There will be a leap second between 051231 235959 & 060101 00 .
>> Does anyone know how the time servers used by NTP handle this ?
>> Is it just left to the local machine to realise it's 1 sec fast
>> & adjust ov
On Sat, 24 Dec 2005 19:33:26 -0500
Philip Webb <[EMAIL PROTECTED]> wrote:
> There will be a leap second between 051231 235959 & 060101 00 .
> Does anyone know how the time servers used by NTP handle this ?
> Is it just left to the local machine to realise it's 1 sec fast
> & adjust over a fe
I do not have a solution to your question, but in general there has
been some discussion in the press [UK] of late that covered this very
issue.
The link has some further links that may lead you to your answer.
http://www.bbc.co.uk/radio4/science/thematerialworld_20051124.shtml
stu
On 25/12/05,
On Sat, Dec 24, 2005 at 07:33:26PM -0500, Philip Webb wrote:
> There will be a leap second between 051231 235959 & 060101 00 .
> Does anyone know how the time servers used by NTP handle this ?
> Is it just left to the local machine to realise it's 1 sec fast
> & adjust over a few hours or doe
There will be a leap second between 051231 235959 & 060101 00 .
Does anyone know how the time servers used by NTP handle this ?
Is it just left to the local machine to realise it's 1 sec fast
& adjust over a few hours or does something else alert it to correct things ?
If the former, it could
14 matches
Mail list logo
