Great Circle Associates Firewalls
(June 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: RE: Year 2000 compliance
From: C Matthew Curtin <cmcurtin @ research . megasoft . com>
Date: Fri, 13 Jun 1997 12:33:37 -0400 (EDT)
To: Bill Stout <stoutb @ pios . com>
Cc: "Stackpole, Bill" <BSTACKPO @ sla . com>, firewalls @ GreatCircle . COM
In-reply-to: <2 . 2 . 32 . 19970612185831 . 00723464 @ vaxf . pios . com>
References: <2 . 2 . 32 . 19970612185831 . 00723464 @ vaxf . pios . com>
Reply-to: cmcurtin @ research . megasoft . com

>>>>> "Bill" == Bill Stout <stoutb @
 pios .
 com> writes:

Bill> I'm not familiar with the 2039 problem.

I've seen a fair bit of confusion about this among the folks who have
some familiarity with it, so lemmie 'splain...

This is a limitation in how Unix implements the clock.  Specifically,
it does so as seconds since epoch (midnight, January 1, 1970), and the
data type used to store that number (a 4 byte signed integer).  A 4
byte signed integer will overflow at 2147483648.  As a result,
2147483648 seconds after the epoch, there will be an overflow, such
that when you make a time() call, you'll get unpredictable results.

In 2039, we'll reach that number of seconds since epoch.

Hope that helps.

--
Matt Curtin  Chief Scientist Megasoft Online  cmcurtin @
 research .
 megasoft .
 com
http://www.research.megasoft.com/people/cmcurtin/    I speak only for myself
Pull AGIS.NET's plug!   Crack DES NOW! http://www.frii.com/~rcv/deschall.htm


Follow-Ups:
References:
Indexed By Date Previous: MS Proxy Server and SOCKS4/ mapped links/ plugs
From: Nick Keenan <nick @ gsionline . com>
Next: Re: secure database access
From: C Matthew Curtin <cmcurtin @ research . megasoft . com>
Indexed By Thread Previous: RE: Year 2000 compliance
From: Bill Stout <stoutb @ pios . com>
Next: RE: Year 2000 compliance
From: Brian Tackett <cym @ acrux . net>

Google
 
Search Internet Search www.greatcircle.com