Subject: | |
From: | |
Reply To: | |
Date: | Thu, 6 Sep 2001 10:52:26 -0700 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Re:
> The real problem will come in 2038, when the SIGNED 32-bit integer will
> in fact overflow. But by then, this being Unix, it will have been
> Now: 0x3b96b178 999731576 Wed Sep 5 19:12:56 2001
> Then: 0x3b9aca00 1000000000 Sat Sep 8 21:46:40 2001
> Then: 0x40000000 1073741824 Sat Jan 10 08:37:04 2004
> Then: 0x7fffffff 2147483647 Mon Jan 18 22:14:07 2038
> And: 0x80000000 -2147483648 Fri Dec 13 15:45:52 1901
(the above times are apparently in Tracy's local (TZ) time)
I used HourGlass to set the date/time to Tue Jan 19 03:14:04 GMT 2038,
which is 3 seconds before the overflow, and then watched what would
happen with the HP-UX "date" command:
(oz#sieler) source/hourglass: date
Tue Jan 19 03:14:04 GMT 2038
(oz#sieler) source/hourglass: date
Tue Jan 19 03:14:07 GMT 2038
(oz#sieler) source/hourglass: date
Fri Dec 13 20:45:52 GMT 1901
(oz#sieler) source/hourglass: date
Fri Dec 13 20:45:53 GMT 1901
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|