On Thu, Feb 9, 2012 at 14:09, David J Taylor <[email protected]> wrote: > "Dave Hart" <[email protected]> wrote in message > news:cambsiydttpdse_jc+5wroq01sydsgowjfjahj7dh_ggydes...@mail.gmail.com... >> Still the big picture is the same. ntpdc kerninfo is particularly >> fragile and should only be used between very similar systems. ntpq >> kerninfo is robust. There is no reasonable way to fix this without >> seriously overhauling ntpdc and ntpd, meaning the fix would only work >> with new ntpdc against new ntpd, and given that ntpq gets it right, it >> doesn't make sense to re-engineer the depracated ntpdc/ntpd mode 7 >> code. > > Thanks for that, Dave, and I appreciate the time taken to answer. When you > write: "All are fixed by new ntpd and ntpq.", what minimum release of ntp > counts as "new"? I hope that my ntpq 4.2.7p241 is "new", but what is the > minimum version of ntpd it will converse correctly with?
I don't know offhand, and I'm in bed. But I will tell you how to find out: http://archive.ntp.org/ntp4/ChangeLog-dev Scan for "kerninfo" to find when ntpq's kerninfo was added or last fixed. Cheers, Dave Hart _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
