If you do not like the X year limit at startup I recommend you lobby for something more to your liking.
I think there are 2 places to lobby: - Dave - The IETF NTP WG I believe Dave's point is that this is trivial to work around - one sets the initial date to be either somewhere between the time the executable was compiled and X years *later* - then ntpd starts up and sets the date correctly. In fact, it will do that for the next X+60ish (unless it's X+30ish) years. I would *love* to see the spec include a flag (could be the stratum, could be something else) that says "The date you are being given is not X.Y (seconds and fractions of seconds), but is X (all seconds)". This will, I believe, solve the problem without making the packets bigger. H _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
