Red Hat Bugzilla – Bug 9248
xntp3 RPM does not call chkconfig (and other bugs)
Last modified: 2008-05-01 11:37:54 EDT
The xntp3 RPM should call chkconfig in %pre and %post scripts, so that the links in /etc/rc.d/rc#.d are made properly. On my system, this causes xntpd to not get shut down properly at system shutdown. You should add something like the following to the spec file: Prereq: chkconfig %post /sbin/chkconfig --add xntpd %preun if [ "$1" = 0 ]; then /etc/rc.d/init.d/xntpd stop /sbin/chkconfig --del xntpd fi There are also 2 spurious patch files left in the documentation for the package: /usr/doc/xntp3-5.93/copyright.html.orig /usr/doc/xntp3-5.93/copyright.html.orig.patd Thanks, Chris Wing wingc@engin.umich.edu
Again, the Right Thing To do. Unfortunately, how xntpd is started is only part of the issue, the rest is how to configure a master server. Since we cannot supply a master NTP server as part of the default configuration, we leave it up to the system administrator to choose a master server and start xntpd.
That makes sense, but you could still call chkconfig to make the appropriate links and then disable xntpd: /sbin/chkconfig --add xntpd /sbin/chkconfig xntpd reset (make sure the init script for xntpd disables it by default in the chkconfig: tag) The problem I had was that even after configuring xntpd and supposedly activating it with ntsysv, it didn't shut down properly because the K##xntpd links were never made. I just verified that this is the case- if no links are present in /etc/rc.d/rc#.d, ntsysv only adds the start links and not the stop links. (maybe I should report this as a bug in ntsysv?) These kinds of things confuse sysadmins.