> > Not being a time geek, since Cisco's were called out for being wild
> > jitter-mongers... how much jitter are we talking about?
> >
> > Clock is synchronized, stratum 2,
> > nominal freq is 250. Hz, actual freq is 249.9989 Hz, precision is
> 2**18
> > reference time
> Not being a time geek, since Cisco's were called out for being wild
> jitter-mongers... how much jitter are we talking about?
>
> Clock is synchronized, stratum 2,
> nominal freq is 250. Hz, actual freq is 249.9989 Hz, precision is 2**18
> reference time is CD6A7CD4.
> From: Deepak Jain
> Date: Tue, 17 Mar 2009 15:54:28 -0400
>
> >
> > As long as the end-user is made aware that the accuracy of said NTP
> > clock
> > is +/- 30.000 seconds (or whatever jitter might exist). Seems kind
> > of
> > ridiculous to use an NTP source that is, for many purposes,
>
> As long as the end-user is made aware that the accuracy of said NTP
> clock
> is +/- 30.000 seconds (or whatever jitter might exist). Seems kind
> of
> ridiculous to use an NTP source that is, for many purposes, wildly
> inaccurate. For my purposes, wildly is more than +/- 0.1 second
On Tue, 17 Mar 2009, valdis.kletni...@vt.edu wrote:
They may suck for being a Stratum-1/2 server, but even the most jittery
Cisco is still far and away good enough to serve up a ntpdate so that an
end-user PC-class machine is in the right minute.
As long as the end-user is made aware that the
On Tue, 17 Mar 2009 08:06:51 PDT, Kevin Oberman said:
> Routers as ntp servers. Yuck! Routers route well, but they treat time as
> a low priority job and jitter on Cisco routers is simply terrible.
> Junipers do better, but are still a poor time server.
They may suck for being a Stratum-1/2 serve
> From: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?=
> Date: Mon, 16 Mar 2009 23:07:42 -0700
>
>
> On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
>
> > We use CDMA clocks and last leap second it took weeks for all of the
> > cell sites to adjust the last one. As a result, I have set all of our
> > cloc
On Tue, Mar 17, 2009 at 1:07 AM, Ask Bjørn Hansen wrote:
>
> On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
>
> We use CDMA clocks and last leap second it took weeks for all of the
>> cell sites to adjust the last one. As a result, I have set all of our
>> clocks for manual leap second and set t
On Dec 31, 2008, at 15:28, Kevin Oberman wrote:
We use CDMA clocks and last leap second it took weeks for all of the
cell sites to adjust the last one. As a result, I have set all of our
clocks for manual leap second and set them to adjust tonight at
midnight
(UTC).I'll take a look in about
On Mon, Jan 5, 2009 at 4:19 PM, Peter Beckman wrote:
>* UTC can get out of whack with the rotation of the earth around the
> sun, because our rotation is not uniform, but is calculated rather
> than measured (well, sort of)
As Crist Clark points out, leap seconds are about the Ear
Peter Beckman wrote:
* GMT is used to imply UT1, but sometimes UTC, but really GMT is just
massively confusing and you shouldn't use it, either in conversation
or in your servers/routers, because nobody is really sure without
reading a lot of documentation what GMT means for
>>> On 1/5/2009 at 1:19 PM, Peter Beckman wrote:
> I've gleened from this thread that:
>
> * everyone uses UTC, or should, because UTC is a uniform time scale,
>except for those leap seconds
Local time is totally appropriate in some circumstances, but it
is pretty much always define
I've gleened from this thread that:
* everyone uses UTC, or should, because UTC is a uniform time scale,
except for those leap seconds
* UTC is sourced from the frequence of a radio emission from cesium
atoms which are extremely constant
* UTC can get out of whack with the
> It's theoretically possible for leap seconds to be introduced
> at the end of March and September.
As I recall, NTP supports leap seconds every month,
for which there is a prediction that even this
would be insufficient at some point in this
millennium (depending, of course, on the actual
rot
On 05/01/2009 6:01, "Nick Hilliard" wrote:
[...]
> But seriously. Leap seconds occur every couple of years, either on July
> 30th and Dec 31. Sometimes both. And sometimes every consecutive year for
> a couple of years on the run.
It's theoretically possible for leap seconds to be introduced
On Jan 5, 2009, at 11:30 AM, Adrian Chadd wrote:
This begs the question - how the heck do timekeepers and politicians
get
away with last minute time changes?
Surely there's -some- pushback from technology related interest
groups to
try and get more than four weeks warning? :)
Having b
Adrian Chadd wrote:
> Wow, how'd I miss that, I wonder? :)
I would recommend lodging a complaint to the relevant authorities. That's
sure to help.
But seriously. Leap seconds occur every couple of years, either on July
30th and Dec 31. Sometimes both. And sometimes every consecutive year for
Adrian Chadd wrote:
> This begs the question - how the heck do timekeepers and politicians get
> away with last minute time changes?
>
> Surely there's -some- pushback from technology related interest groups to
> try and get more than four weeks warning? :)
>
>
>
> Adrian
>
>
The first notice
On Mon, Jan 05, 2009, Nick Hilliard wrote:
> Notice for the leap second was issued on July 4 2008.
>
> http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.36
>
Wow, how'd I miss that, I wonder? :)
I'm just angry at the jack moves pulled by last minute timezone changes
back in Australia, and the mas
On Tue, Jan 06, 2009 at 01:30:51AM +0900, Adrian Chadd wrote:
> This begs the question - how the heck do timekeepers and politicians get
> away with last minute time changes?
>
> Surely there's -some- pushback from technology related interest groups to
> try and get more than four weeks warning? :
Adrian Chadd wrote:
> This begs the question - how the heck do timekeepers and politicians get
> away with last minute time changes?
>
> Surely there's -some- pushback from technology related interest groups to
> try and get more than four weeks warning? :)
?
Notice for the leap second was issue
This begs the question - how the heck do timekeepers and politicians get
away with last minute time changes?
Surely there's -some- pushback from technology related interest groups to
try and get more than four weeks warning? :)
Adrian
On Mon, Jan 05, 2009, Frank Bulk wrote:
> A report from a D
A report from a DHCP/DNS appliance vendor here:
Several customers have reported a complete lock-up of their Proteus system
around the beginning of January 1st 2009. We believe that we have traced
this to a problem in the underlying kernel and NTP and the handling of the
date ch
On Thu, 1 Jan 2009, Simon Lockhart wrote:
My Oracle boxes that rebooted were running RAC (version 10G R2), too. Another
Solaris 10 box running the same version of Oracle, but not RAC, did not reboot.
Looks rather like an Oracle 10 RAC bug.
It's a known bug in Oracle 10. When the time is set ba
Steven Saner wrote:
> Jon Meek wrote:
>> My Solaris 10 boxes are all happy (and did not reboot). I monitor NTP
>> on a number
>> of devices, including one router. The router was off by one second for
>> a while, but
>> is OK after an hour. Everything else was fine immediately.
>>
>> In 2005, our CD
Once upon a time, Steven Saner said:
> I run a bunch of Slackware Linux boxes of varying versions. As best as I
> can tell, at or around 00:00 UTC all of my Slackware 12.0 boxes crashed
> with a kernel panic. I don't think it is ntpd because it is the same
> version as on 12.1 boxes (4.2.4p0) t
Jon Meek wrote:
My Solaris 10 boxes are all happy (and did not reboot). I monitor NTP
on a number
of devices, including one router. The router was off by one second for
a while, but
is OK after an hour. Everything else was fine immediately.
In 2005, our CDMA clock got the leap second between 15:
out to
log.
--Original Message--
From: Simon Lockhart
Sender:
To: Wil Schultz
Cc: NANOG list
Sent: Jan 1, 2009 8:13 AM
Subject: Re: Leap second tonight
On Thu Jan 01, 2009 at 07:58:21AM -0800, Wil Schultz wrote:
> All of my Solaris 10 boxes stayed up with the exception of the Ora
On Thu, Jan 01, 2009 at 04:13:51PM +, Simon Lockhart wrote:
> On Thu Jan 01, 2009 at 07:58:21AM -0800, Wil Schultz wrote:
> > All of my Solaris 10 boxes stayed up with the exception of the Oracle
> > 10g RAC boxes.
>
> My Oracle boxes that rebooted were running RAC (version 10G R2), too. Ano
On Thu Jan 01, 2009 at 07:58:21AM -0800, Wil Schultz wrote:
> All of my Solaris 10 boxes stayed up with the exception of the Oracle
> 10g RAC boxes.
My Oracle boxes that rebooted were running RAC (version 10G R2), too. Another
Solaris 10 box running the same version of Oracle, but not RAC, did n
All of my Solaris 10 boxes stayed up with the exception of the Oracle
10g RAC boxes.
db1:~ wschultz$ uname -a
SunOS db1 5.10 Generic_137111-01 sun4u sparc SUNW,Sun-Fire-V490
A friend of mine had his RAC boxes reboot as well, similar
configuration. I've poured through the logs and see normal
On Thu Jan 01, 2009 at 04:29:35AM -0500, Jim Popovitch wrote:
> Have either of you determined if this was a OS reboot and not a bios reset?
I've been trawling through all the logfiles I can find on the box, and I see
normal entries up until 23:59:xx, and then the next entry is stuff restarting.
Co
On Thu, Jan 1, 2009 at 04:15, Simon Lockhart wrote:
> On Wed Dec 31, 2008 at 04:53:57PM -0800, Wil Schultz wrote:
>> At which point my Solaris 10 v490's reboot in unison, lovely.
>>
>> Anyone else see anything interesting?
>
> I had a couple of Oracle servers (Solaris 10) reboot a couple of minute
On Wed Dec 31, 2008 at 04:53:57PM -0800, Wil Schultz wrote:
> At which point my Solaris 10 v490's reboot in unison, lovely.
>
> Anyone else see anything interesting?
I had a couple of Oracle servers (Solaris 10) reboot a couple of minutes
just before the leap second. All my other Solaris 10 boxes
On Wed, 31 Dec 2008 16:53:57 -0800
Wil Schultz wrote:
> At which point my Solaris 10 v490's reboot in unison, lovely.
>
Solaris? Or ZuneOS? (See
http://www.nytimes.com/2009/01/01/technology/personaltech/01zune.html)
--Steve Bellovin, http://www.cs.columbia.edu/~smb
It looks like clepsydra hasn't been updated:
address ref clock st when poll reach delay offsetdisp
-~192.5.41.40 .USNO.1 194 1024 37741.15.1938.2
-~130.207.244.240 .GPS. 168 1024 37723.1 11.09 1.3
~127.127.7.1
My Solaris 10 boxes are all happy (and did not reboot). I monitor NTP
on a number
of devices, including one router. The router was off by one second for
a while, but
is OK after an hour. Everything else was fine immediately.
In 2005, our CDMA clock got the leap second between 15:08 and 15:38
EST c
At which point my Solaris 10 v490's reboot in unison, lovely.
Anyone else see anything interesting?
-wil
On Dec 31, 2008, at 4:01 PM, Peter Lothberg wrote:
bash-2.05b# date
Thu Jan 1 00:59:58 CET 2009
bash-2.05b# date
Thu Jan 1 00:59:59 CET 2009
bash-2.05b# date
Thu Jan 1 00:59:60 CET 2009
bash-2.05b# date
Thu Jan 1 00:59:58 CET 2009
bash-2.05b# date
Thu Jan 1 00:59:59 CET 2009
bash-2.05b# date
Thu Jan 1 00:59:60 CET 2009
bash-2.05b# date
Thu Jan 1 01:00:00 CET 2009
bash-2.05b# date
Thu Jan 1 01:00:01 CET 2009
bash-2.05b#
-P
> From: Kevin Day
> Date: Wed, 31 Dec 2008 16:41:39 -0600
>
>
> Just a reminder that there's a leap second tonight.
>
> Last time I watched for what happened on 01/01/2006, there was a
> little bit of chaos:
> http://markmail.org/message/cpoj3jw5onzhhjkr?q=%22kevin+day%22+leap+second+reminde
On Wed, Dec 31, 2008 at 04:41:39PM -0600, Kevin Day wrote:
> I've been told that some of the causes of these problems are fixed on
> any reasonably recent ntp distribution, but just in case, you might
> wanna keep an eye out if you're seeing any weirdness. The worst damage
> I'd heard from an
Since leap seconds apply to UTC, won't the leap second be in about 22
minutes?
-jasper
On 1/01/2009, at 11:41 AM, Kevin Day wrote:
Just a reminder that there's a leap second tonight.
Last time I watched for what happened on 01/01/2006, there was a
little bit of chaos: http://markmail.org
INTERNATIONAL EARTH ROTATION AND REFERENCE SYSTEMS SERVICE (IERS)
SERVICE INTERNATIONAL DE LA ROTATION TERRESTRE ET DES SYSTEMES DE REFERENCE
SERVICE DE LA ROTATION TERRESTRE
OBSERVATOIRE DE PARIS
61, Av. de l'Observatoire 75014 PARIS (France)
Tel.
44 matches
Mail list logo
