question about upgrading from Classic to NTPsec (packaging issue)

Eric S. Raymond esr at
Mon Jul 4 17:23:16 UTC 2016

John D. Bell <JDB at>:
> Do we want to install NTPsec in the same hierarchy as Classic?  Or in an
> alternative location?  (/usr/local?  /opt??)

Same hierarchy. The last thing we want is bug reports due to an accidentally
mixed installation...

> So far, the config files are compatible so it makes sense to leave the old
> > one alone if it has been edited.  (The admin might have picked some good
> > servers or setup logging.)
> >
> Yes.  Another method is to do like a standard RPM upgrade script does, and
> only clobber the existing config file *if* it is unchanged from the last
> version's
> distributed version.  Any changes cause the new config file to be dropped
> into the directory with a "-rpmnew" suffix.  Then the admin has to resolve
> conflicts manually.


> > Where would you document what happened and/or how to switch back?
>  Good question.  Suggestions?

Some documentation file  in /usr/share/ntpsec - READNE-UPGRADE or
		<a href="">Eric S. Raymond</a>

More information about the devel mailing list