Date: 26 Aug 1998 23:59:01 +0200 From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) To: "Susan R. O'Brien" <srobrien@mss.lucent.com> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K problem Message-ID: <xzpzpcre76i.fsf@olvaldi.ifi.uio.no> In-Reply-To: "Susan R. O'Brien"'s message of "Wed, 26 Aug 1998 15:35:25 -0400" References: <35E4637C.5E26EEC3@mss.lucent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Susan R. O'Brien" <srobrien@mss.lucent.com> writes: > I'm using 2.2.5 and was looking at the source code for localtime and > asctime. They're using a #define TM_YEAR_BASE 1900. > > This looks to be a bit of a problem for Y2K compliancy! No. Read the man page. FWIW, FreeBSD does have Y2K problems. Grep (glimpse) the source tree for calls to localtime(3) and audit every bit of code that calls it. I've read through date(1) and pax(1), and they both have problems (and ugly kludges trying to work around these problems). BTW, most of the date-related code in pax(1) looks cut'n'pasted from date(1). Maybe we need an audit... DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpzpcre76i.fsf>