On (2012-07-03 16:53 -0700), Owen DeLong wrote:
Sure, but even with that, 99% of it has only a passing 'interesting' effect
and
then recovers.
Inclusive you no longer know order of events based on your logs, and
virtually none of your software are logging 60th second.
What are only
Hi,
Anybody using Arbor Peakflow? Can tell us about its efficiency? Any other DDoS
detection and mitigation product ?
Regards,
WaseemÂ
Tyler Haske tyler.ha...@gmail.com writes:
Someone running an NTP Server connected to a cesium clock could run
the leap-second time code. Since its *their job* to have the correct
time, they can do all the fancy rarely used things that make parts of
the Internet die every couple of years.
Tell that to people in the third world without utilities.
On Jul 3, 2012 8:32 PM, Randy Bush ra...@psg.com wrote:
Also, I don't think there is an acceptable level of downtime for
water.
coming soon to a planet near you
randy
On 7/4/12, Robert E. Seastrom r...@seastrom.com wrote:
[snip]
Local clocks have to be consulted much too frequently (logging,
timestamping, etc) for just put it in the cloud to work.
You might want to read up on NTP (wikipedia provides a reasonable
introduction).
The NTP daemon could still
On 2012 Jul 4, at 08:50, Jimmy Hess wrote:
So accept the inaccuracy and correct the clock in the normal way that
NTP corrects clocks that have drifted.
This is basically the leap smear that google instituted after
the issues in 2005. It works nicely in cloud applications where
real-time is
On Wed, Jul 4, 2012 at 8:50 AM, Jimmy Hess mysi...@gmail.com wrote:
The NTP daemon could still provide a configuration option to not
implement leap-seconds locally, or ignore the leap-second
announcement received. So the admin can make a tradeoff favoring
Stability over Correctness, of
On Tue, Jul 03, 2012 at 04:54:24PM -0400, valdis.kletni...@vt.edu wrote:
On Tue, 03 Jul 2012 21:49:40, Peter Lothberg said:
Leapseconds can be both positive and negative, but up to now, the
earth has only slowed down, so we have added seconds.
That's what many people believe, but it's
On Wed, 04 Jul 2012 12:44:40 -0500, Brett Frankenberger said:
Leap Seconds and Leap Years are completely unrelated and solve two
completely different problems.
Leap Seconds exist to adjust time to match the Earth's actual rotation.
They exist because the solar day is not exactly 24 hours.
On Wed, Jul 4, 2012 at 1:44 PM, Brett Frankenberger rbf+na...@panix.com wrote:
Without leap seconds, the sun stops being overhead at noon.
But that's ridiculous. The sun *isn't* overhead at noon except at one
particular longitude within each time zone. Everywhere else time synch
to local noon is
On Wed, Jul 04, 2012 at 06:10:45PM -0400, William Herrin wrote:
On Wed, Jul 4, 2012 at 1:44 PM, Brett Frankenberger rbf+na...@panix.com
wrote:
Without leap seconds, the sun stops being overhead at noon.
But that's ridiculous. The sun *isn't* overhead at noon except at one
particular
Tell that to people in the third world without utilities.
Also, I don't think there is an acceptable level of downtime for
water.
coming soon to a planet near you
i work there regularly. the typical nanog kiddie does not.
randy
On Jul 4, 2012, at 3:29 PM, Jason Hellenthal jhellent...@dataix.net wrote:
Yeah but what you don't understand is that manual navigation after a
certain point of difference becomes inaccurate to a degree that is
unacceptable by most military standards.
Manual navigation (sextant, etc) is
On Wed, Jul 04, 2012 at 05:02:02PM -0400, valdis.kletni...@vt.edu wrote:
On Wed, 04 Jul 2012 12:44:40 -0500, Brett Frankenberger said:
Leap Seconds and Leap Years are completely unrelated and solve two
completely different problems.
Leap Seconds exist to adjust time to match the Earth's
On Wed, 04 Jul 2012 21:01:50 -0500, Brett Frankenberger said:
No. Leap Years arise because the solar year is not an integral
multiple of the solar day.
And leap seconds arise because the astronomical day is not
an integral multiple of the hour, minute, or second. Same problem.
still hold.
On 7/4/12, William Herrin b...@herrin.us wrote:
IMO, leap seconds are a really bad idea. Let the vanishingly few
people who care about a precision match against the solar day keep
track of the deviation from clock time and let everybody else have a
*simple* clock year after year. When the
On Jul 4, 2012, at 8:39 PM, Jimmy Hess wrote:
On 7/4/12, William Herrin b...@herrin.us wrote:
IMO, leap seconds are a really bad idea. Let the vanishingly few
people who care about a precision match against the solar day keep
track of the deviation from clock time and let everybody else
http://www.bbc.com/news/technology-18704192
This is very good news, IMHO. And operationally relevant, even to North
American operators.
--
TTFN,
patrick
Rather than discussing the pros and cons of UTC and leap seconds, just
create your own time system.
You could call it OpenTime. OpenTime will use NTP servers where the
Stratum 1 servers are synced to some time standard that doesn't care
about leap seconds. That way the consumer can chose to
On 7/5/2012 12:47 AM, Roy wrote:
Rather than discussing the pros and cons of UTC and leap seconds, just
create your own time system.
You could call it OpenTime. OpenTime will use NTP servers where the
Stratum 1 servers are synced to some time standard that doesn't care
about leap seconds.
On 7/4/2012 10:06 PM, Peter Kristolaitis wrote:
On 7/5/2012 12:47 AM, Roy wrote:
Rather than discussing the pros and cons of UTC and leap seconds,
just create your own time system.
You could call it OpenTime. OpenTime will use NTP servers where the
Stratum 1 servers are synced to some time
On 7/4/12 8:48 PM, Owen DeLong wrote:
Given that we don't seem to be able to eliminate the absurdity of DST,
I doubt that either of those proposals is likely to fly. Owen
Before we had timezones your clock offset was forward or backward 4
minutes every-time you crossed a meridian.
22 matches
Mail list logo
