Nicolas Williams wrote:
> On Fri, Apr 17, 2009 at 02:48:43PM -0400, Brian Utterback wrote:
>> Nicolas Williams wrote:
>>> you
>>> mentioned some incompatible changes.  Can you list them all?  
>> To answer this, please find enclosed a list of all the 
>> incompatibilities I know of.
> 
> How is upgrade handled?  Are old configs re-written to the new style on
> service start?


No. Because of the fact that the ntp.conf file is almost completely 
backwards compatible, we will not attempt to re-write the files. At 
your request, I have added a check for the obsolete "authentication 
no" configuration line, and if found will disable the authentication 
requirement.

The only reason to use "disable pll" was to get the slewalways option 
to work. Since the --slew option now automatically sets the kernel 
loop to disable, the "disable pll" option can safely be ignored.

The "enable/disable pps" option is really never used, since it implies 
that a hardware refclock is in use (which cuts the percentage down to 
a very small number right there) and that the PPS signal is wired 
(still smaller) and that the customer has gone to that trouble and now 
does not want to use it (I'd be surprised if we hear from even one).

To answer your questions in another leaf of this thread, I would 
prefer "Uncommitted Obsolete" for ntpdc and ntpdate rather than 
"Committed Obsolete". I would like the possibility of removing them 
someday, when the NTP distro drops them. It would be most difficult to 
upgrade later if we needed to deliver something that isn't in the distro.

If you really want a link from xntpdc to ntpdc, I am okay with that. 
Does anybody besides Nico like that idea?



-- 
blu

"You would think that spies would have to be light sleepers, but
that isn't true. For instance, James Bond once slept through an
earthquake. That's right, he was shaken but not stirred."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom

Reply via email to