Hi,
I'm using redhat 7.4 and in bits/types.h time_t is defined as long int.
This causes a wrap in 2038 (as I'm sure you all know). I searched the
redhat site for date 2038 and found very little current stuff. The
attached post from 1998 seems to say 'all will be well' but I'm having a
hard time persuading my boss that it's clever to use a date system that
expires in 35 years. I need both date and time. I can write my own date
to/from string routines. What I don't want to do is write the equivalent
of the time() function to get the current date & time. Is there a 64 bit
version of time() available for the current version(s) of linux? Does
anyone have any other ideas?
Thanks,
Andy.
From: rick hamell <hamellr dsinw com>
To: redhat-install-list redhat com
Subject: Re: Y2.038K ISSUES -was Re: Y2K Issues
Date: Sun, 11 Oct 1998 17:03:54 -0700 (PDT)
--------------------------------------------------------------------------------
> my question is/was not about y2k per se but about YEAR 2038 COMPLIANCE.
> is the unix/linux community doing anything to address this issue? How
> long will we/they wait?
Ahh, my understanding is that date is a 32 bit number, so it
stands to reason that when we change to a 64 bit operating system, the
number will change also. For Linux I don't know when that will be, but
FreeBSD will supposedly be there in version 3.2 (3.0 is due out in days
:)
So I'd guess that it'll be soon!
Rick
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
