Jimmy Hess writes:
> On Wed, Jul 1, 2015 at 12:38 AM, Mikael Abrahamsson wrote:
> > quickly. Either we should abolish the leap second or we should make leap
> > second adjustments (back and forth) on a monthly basis to exercise the code
> .
>
> See maybe there should some day be building cod
conf. If
>> it's leep second related.
>>
>> --Original Message--
>> From: Stefan
>> Sender: NANOG
>> To: frnk...@iname.com
>> Cc: nanog@nanog.org
>> Subject: Re: leap second outage
>> Sent: Jun 30, 2015 23:30
>>
>> This
And just 12.5% of them required TLC. =)
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of frnk...@iname.com
Sent: Wednesday, July 01, 2015 7:05 AM
To: 'Stefan'
Cc: nanog@nanog.org
Subject: RE: leap second outage
Yes, happened at 7 pm Central
the
> extra second. I know a large carrier in Israel is down. Waiting for conf. If
> it's leep second related.
>
> --Original Message--
> From: Stefan
> Sender: NANOG
> To: frnk...@iname.com
> Cc: nanog@nanog.org
> Subject: Re: leap second outage
> Se
On Wed, Jul 1, 2015 at 12:38 AM, Mikael Abrahamsson wrote:
> quickly. Either we should abolish the leap second or we should make leap
> second adjustments (back and forth) on a monthly basis to exercise the code.
See maybe there should some day be building codes for
commercially marketed sof
Yes, happened at 7 pm Central (0:oo UTC).
From: Stefan [mailto:netfort...@gmail.com]
Sent: Tuesday, June 30, 2015 10:30 PM
To: frnk...@iname.com
Cc: nanog@nanog.org
Subject: Re: leap second outage
This was supposed to have happened @midnight UTC, right? Meaning that we are
past that
Mikael Abrahamsson wrote:
> This is similar to the jiffycounter wrapping, since this doesn't happen
> that often, it's not commonly tested for. Good way is to start the jiffy
> counter so it wraps after 10 minutes of uptime. That way you'll run into
> any bugs quickly. Either we should abolish
oracle linux did this
Jul 1 02:01:29 oraclelinux ntpd[600]: 0.0.0.0 061c 0c clock_step -1.006445 s
Jul 1 02:01:29 oraclelinux ntpd[600]: 0.0.0.0 0615 05 clock_sync
Jul 1 02:01:29 oraclelinux systemd: Time has been changed
Jul 1 02:01:30 oraclelinux ntpd[600]: 0.0.0.0 c618 08 no_sys_peer
all see
Mikael Abrahamsson writes:
> This is similar to the jiffycounter wrapping, since this doesn't happen
> that often, it's not commonly tested for. Good way is to start the jiffy
> counter so it wraps after 10 minutes of uptime. That way you'll run into
> any bugs quickly. Either we should abolish
On Wed, 1 Jul 2015, Jean-Francois Mezei wrote:
However, in systems that expect tightly synchronized clocks, they would
want all the nodes to make the NTP adjustement at the same time.
This is both an operating system and application problem.
http://infiniteundo.com/post/25326999628/falsehoods
On 15-07-01 00:47, Harlan Stenn wrote:
> What I'm about to say may not be as stupid as it sounds: The problems
> here aren't problems for cases where it's not a problem. It is a
> problem where it *is* a problem.
In fairness, systems should be used to NTP making adjustments to the
system clock
Joe writes:
> A leap sec causing issues. For about 40 years now, there have been
> these leap seconds to no real issue. All of these are "go-forwards"
No, they're all "go-backwards" events. That's no big deal to things
that don't care about monotonic time, or to folks who aren't in
violation of s
A leap sec causing issues. For about 40 years now, there have been
these leap seconds to no real issue. All of these are "go-forwards"
and even MS AD (I believe) treat them as a little bump (nothing to see
here move along). So unless you have really a tight VPN (non-standard
conforming) I'd hope th
Correct, the leap second gets inserted at midnight UTC.
"Leap seconds can be introduced in UTC at the end of the months of December
or June, depending on the evolution of UT1-TAI. Bulletin C is mailed every
six months, either to announce a time step in UTC or to confirm that there
will be no t
No. Some one leaked some routes:
https://mobile.twitter.com/Axcelx/status/616058414746202113
Regards,
Dovid
-Original Message-
From: Justin Paine
Date: Tue, 30 Jun 2015 20:37:06
To:
Cc: Stefan; NANOG;
;
Subject: Re: leap second outage
Any confirmation if the AWS outage was leap
That is my understanding as well. The event was about 3.5 hours ago.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Tue, Jun 30, 2015 at 11:30 PM, Stefan wrote:
> This was supposed to have happened @midnight UTC, right? Meaning that we
> are
I read that and that at midnight local time since that's when you have the
extra second. I know a large carrier in Israel is down. Waiting for conf. If
it's leep second related.
--Original Message--
From: Stefan
Sender: NANOG
To: frnk...@iname.com
Cc: nanog@nanog.org
Subject
This was supposed to have happened @midnight UTC, right? Meaning that we
are past that event. Under which scenarios should people be concerned about
midnight local time? Lots of confusing messages flying all over...
On Jun 30, 2015 10:13 PM, wrote:
> We experienced our first leap second outage --
18 matches
Mail list logo
