question about upgrading from Classic to NTPsec (packaging issue)

John D. Bell JDB at
Tue Jul 5 20:00:39 UTC 2016

Gary and Eric,

    I just installed the "ntp" and "ntpdate" packages on CentOS 6.6 from
the distribution's repo.  This is the arch on which I'm building the RPM,
because it was easy to spin up.

    The executables ended up in /usr/sbin (except for ntpstat, which ended
up in /usr/bin).  Drift file in /var/lib/ntp/drift; statistics in
/var/log/ntpstats.  Main config file in /etc/ntp.conf, other bits'n'bobs of
config in other places in /etc.  :P  ISTR that if you download the Classic
source code from, configure it with the defaults, then build and
install it, the results do end up in the /usr/local hierarchy.  What a mess!

    I agree with Eric's previous recommendation to *not* install in a
different place (to prevent error reports from a "mixed" install), but I'm
leaning towards having NTPsec's initial RPM file put things into
/usr/local, and using the /etc/alternatives symlink trick to pick out the
'right' version.  And of course having an uninstall script which backs it
all out, and undoes the symlink indirection.


  - *John D. Bell*

On Mon, Jul 4, 2016 at 6:57 PM, Gary E. Miller <gem at> wrote:

> Yo John!
> On Mon, 4 Jul 2016 11:00:54 -0400
> "John D. Bell" <JDB at> wrote:
> > Do we want to install NTPsec in the same hierarchy as Classic?  Or in
> > an alternative location?  (/usr/local?  /opt??)
> The default for NTP Classic is /usr/local/.  Keep that.
> Only distros should put things in /usr/
> OTOH, any RedHat RPM should likely over-write Classic.
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         gem at  Tel:+1 541 382 8588
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the devel mailing list