[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090107095419.70b78dc7@lxorguk.ukuu.org.uk>
Date: Wed, 7 Jan 2009 09:54:19 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: David Newall <davidn@...idnewall.com>
Cc: Nick Andrew <nick@...k-andrew.net>,
Linas Vepstas <linasvepstas@...il.com>, david@...g.hm,
Kyle Moffett <kyle@...fetthome.net>,
Ben Goodger <goodgerster@...il.com>,
Robert Hancock <hancockr@...w.ca>,
linux-kernel@...r.kernel.org,
"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
> The range of signed 32-bit times is 1901 through 2039, which has only
> one century, 2000, which is a leap year. So the caveat for leap years
> is correct but unnecessary.
The standard however (and library code) were updated many years ago, so
the description is still wrong.
> So I've discoverd, at least on Ubuntu, something wonderful and
> reassuring. It already works exactly the way I think is correct. Look:
> I create a test timezone with no daylight saving and one leap second:
This is entirely configurable - see my earlier post about the "right" and
posix timezones. Really however that belongs on the glibc list.
As far as the kernel and leapseconds go - remember the kernel RTC support
does not know about leap seconds
--
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