[ntp:questions] ntpd sets clock to the year 1939

Robert Dodier robert.dodier at gmail.com
Mon Mar 26 20:37:06 UTC 2007


On Mar 26, 12:50 pm, "Richard B. gilbert" <rgilber... at comcast.net>
wrote:

> I believe that there is a limit to the date/time range that ntpd can
> handle and that it's something like 36 years.  Try setting the date
> manually to something a little closer to being current.  If it's off by
> less than 36 years, I think ntpd will handle it correctly.  A startup
> script that set the date to a reasonable approximation; e.g. 2007 would
> probably solve your problem and work for the next 36 years or so.

Yes! That's it. I set the date by hand to Jan 1, 2007, and then ntpd
was
able to handle the rest. It seems odd to me that ntpd gets confused by
too large a time difference, but oh well, it's OK the way it is.

Thanks for your help,
Robert Dodier




More information about the questions mailing list