On 3/6/2012 2:28 AM, Phil Fisher wrote:
> I would appreciate help since we need to cover the scenario where our
> 2.6.9 Linux kernel
> may crash/hang when a leap Second insert occurs (due to the printk bug).
>
> Some context to avoid repetitive simple answers along lines of upgrade XYZ:
> * we cann
On Wed, May 9, 2012 at 3:12 PM, Phil Fisher wrote:
> Once this was done, then ntptime indicates that it has been set even if the
> current status shows it is not. In my opinion this is at best fallacious if
> not a bug. If the Leap indicator is cleared then I would not expect it to be
> remem
g the leap second event.
Phil
-Original Message-
From: Dave Hart [mailto:h...@ntp.org]
Sent: 09 May 2012 15:24
To: Phil Fisher
Cc: questions@lists.ntp.org
Subject: Re: [ntp:questions] Leap Second testing
On Wed, May 9, 2012 at 8:44 AM, Phil Fisher wrote:
> I was using ntptime to
On Wed, May 9, 2012 at 8:44 AM, Phil Fisher wrote:
> I was using ntptime to set the status bits for a system running a server
> (Centos 5, ntpd 4.2.2p1). Tis allowed me to set the LI indicator and
> apparently to clear it. The output from ntptime is shown at the end of this
> message. When I loo
Hi folks
Some of you may recall a question I posted several weeks ago (and to which
principally Dave Hart replied) about Leap Second and a testing scenario for our
systems.
I am processing this at the moment and found what seems to be interesting
information, unexpected to me.
I was using ntpt
