Patrick Drolet @
GALEA NETWORK SECURITY
06/14/97 05:08 PM
On Fri, 13 Jun 1997, C Matthew Curtin wrote:
> 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.
unsigned 32 bit number would provide EPOCH+136 years, (year 2106)
It think Unix time() can still be reliable for a while...
======================================================
Patrick Drolet / Galea Network Security / 514.923.0555
These opinions are my own and shall remain that way.
======================================================
The reasonable man adapts himself to the world; the
unreasonable one persists in trying to adapt the world
to himself. Therefore, all progress depends on the
unreasonable man. - G. B. Shaw
======================================================
Follow-Ups:
|
|
