[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f73f7ab80901040926t49ec20f5oac8750813bfb3622@mail.gmail.com>
Date: Sun, 4 Jan 2009 12:26:56 -0500
From: "Kyle Moffett" <kyle@...fetthome.net>
To: "Sitsofe Wheeler" <sitsofe@...oo.com>
Cc: david@...g.hm, "David Newall" <davidn@...idnewall.com>,
"Ben Goodger" <goodgerster@...il.com>,
"Robert Hancock" <hancockr@...w.ca>, linux-kernel@...r.kernel.org,
linasvepstas@...il.com, "Jeffrey J. Kosowsky" <jeff@...owsky.org>,
MentalMooMan <slashdot@...eshallam.info>,
"Travis Crump" <pretzalz@...hhouse.org>, burdell@...ntheinter.net
Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009
On Sun, Jan 4, 2009 at 11:15 AM, Sitsofe Wheeler <sitsofe@...oo.com> wrote:
> Windows is also known not to do it without slewing:
> http://www.meinberg.de/english/info/leap-second.htm#os .
Well... Microsoft "[does] not guarantee and [does] not support the
accuracy of the W32Time service between nodes on a network. The
W32Time service is not a full-featured NTP solution that meets
time-sensitive application needs." (See
http://support.microsoft.com/kb/939322). The w32time daemon is not
guaranteed to be within a few seconds of UTC at *any* time of the
year, let alone immediately after a leap-second. In addition, windows
does not have any built-in interpolation between timer ticks, so time
increases in ~15ms steps regardless of how accurate your clock is.
Cheers,
Kyle Moffett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists