David Malone writes: > Indeed - you need to have a timestamp within about ten years of > correct before you start up, otherwise the problem will be worse. Ntp > has the same problem in figuring out the ntp epoch, though we've yet > to see an ntp timestamp wrap around.
ntp-dev has a fix for this problem - while the original solution was "make sure the clock is correct to within ~65 years' time" the new code uses a "date of compile" value, and needs the system time to be either 10 years' before that date or up to 128 years' after that date. See http://bugs.ntp.org/show_bug.cgi?id=1995 for more information (thanks, Juergen!). H _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
