From: Bill Thompson (wht@NEO.RR.COM)
Date: Sat Jan 03 2004 - 23:19:18 EST
This is a well know "issue". Unix keeps its time in the form of
"seconds-since-the-epoch" (January 01, 1970 UCT). This time is kept in a 32
bit variable which will reach its maximum (2147483647) in 2038.
However, 2038 is 34 years from now. Think how much has changed in the
computer world since 1970 (34 years ago). Unix, as we know it, may not even
exist but if it does survive the issue will surly have been solved.
As for me, I'll be laying on a beach somewhere laughing about the "Y2K+38
catastrophe"! :-)
Bill Thompson
Sr UNIX Systems Administrator
The Goodyear Tire & Rubber Co.
Contains Confidential and/or Proprietary Information
May Not Be Copied or Disseminated Without Express Consent of The Goodyear
Tire & Rubber Company.
AIX-L Archives: http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
----- Original Message -----
From: "Wesley Joyce" <wjoyce@UVI.EDU>
Newsgroups: bit.listserv.aix-l
To: <aix-l@Princeton.EDU>
Sent: Saturday, January 03, 2004 10:36 PM
Subject: AIX and 2038?
> I know this issue is real far off, but I ran across some info on this
> during the holiday break. I probably won't be retired in 2038, so it will
> directly affect me. :)
>
> http://maul.deepsky.com/%7Emerovech/2038.html
>
> Both my AIX 4.3.3 and 5.2 boxes stop incrementing time after "Tue Jan 19
> 03:14:07 2038" using the PERL script below.
>
> #!/usr/bin/perl
> # I've seen a few versions of this algorithm
> # online, I don't know who to credit.
> # Comments are by William Porquet
> # http://www.2038.org/
> # You may need to change the line above to
> # reflect the location of your Perl binary
> # (e.g. "#!/usr/local/bin/perl").
> # Also change this file's name to '2038.pl'.
> # Don't forget to make this file +x with "chmod".
> # On Linux, you can run this from a command line like this:
> # ./2038.pl
> use POSIX;
> # Use POSIX (Portable Operating System Interface),
> # a set of standard operating system interfaces.
> $ENV{'TZ'} = "GMT";
> # Set the Time Zone to GMT (Greenwich Mean Time) for date calculations.
> # Now count up in seconds of Epoch time just before and after the
> # critical event. Print out the corresponding date in Gregrorian calendar
> # for each result. Does the year jump backward to some other year
> # than 2038?
> for ($clock = 2147483641; $clock < 2147483651; $clock++)
> {
> print $clock; #I ADDED THIS MYSELF BEFORE RUNTIME. WESLEY JOYCE
> print ctime($clock);
> }
>
> joycew@servera P650:/home/joycew[PROD]> ./2038.pl
> 2147483641Tue Jan 19 03:14:01 2038
> 2147483642Tue Jan 19 03:14:02 2038
> 2147483643Tue Jan 19 03:14:03 2038
> 2147483644Tue Jan 19 03:14:04 2038
> 2147483645Tue Jan 19 03:14:05 2038
> 2147483646Tue Jan 19 03:14:06 2038
> 2147483647Tue Jan 19 03:14:07 2038
> 2147483648Tue Jan 19 03:14:07 2038
> 2147483649Tue Jan 19 03:14:07 2038
> 2147483650Tue Jan 19 03:14:07 2038
>
----------------------------------------------------------------------------
---- > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.558 / Virus Database: 350 - Release Date: 1/2/2004 >
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:26 EDT