[ntp:questions] Re: NTP, Unix and the 34-year itch (better read this)

David L. Mills mills at udel.edu
Fri Jan 23 04:10:15 UTC 2004


See www.eecis.udel.edu/~mills/y2k.htm. If you have a file system that
has ever been written with one or more correct filestamps, use one of
those filestamps and explicitly set the clock. But then, it doesn't
matter as long as you set the clock within 34 years of UTC, like 1 Jan


"Thomas A. Horsley" wrote:
> >Almost all computers of today have some means, such as a time-of-year
> >(TOY) chip, to set the system clock at power up or reboot surely within
> >within 34 years, but some embedded systems do not.
> Speaking of 34 years, my little NTPTime client has the following
> magic number built into it:
> #define JAN_1_1900 2415021L
> Which is the julian day number of the base date for NTP timestamps.
> Obviously once we roll into a new 64 bit chunk of time, I'll need a
> new base date.
> Anyone know what the actual constant is for the next date coming up?
> --
> >>==>> The *Best* political site <URL:http://www.vote-smart.org/> >>==+
>       email: Tom.Horsley at worldnet.att.net icbm: Delray Beach, FL      |
> <URL:http://home.att.net/~Tom.Horsley> Free Software and Politics <<==+

More information about the questions mailing list