Bug 142926 - multiple problems with ntpd init.d script
Summary: multiple problems with ntpd init.d script
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ntp
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Miroslav Lichvar
QA Contact: Brian Brock
Depends On:
Blocks: 181409
TreeView+ depends on / blocked
Reported: 2004-12-15 00:45 UTC by James Ralston
Modified: 2007-11-30 22:07 UTC (History)
0 users

Clone Of:
Last Closed: 2006-08-10 18:24:38 UTC

Attachments (Terms of Use)
patch for /etc/rc.d/init.d/ntpd (1.14 KB, patch)
2004-12-15 00:47 UTC, James Ralston
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0393 normal SHIPPED_LIVE Low: ntp security update 2006-08-10 04:00:00 UTC

Description James Ralston 2004-12-15 00:45:02 UTC
The ntpd init.d script tries to take what was specified for the ntpd
-u option and pass it to ntpdate as the -U option.  This will fail if
the ntpd -u option specified an (optional) group.

The chroot option changed from -T to -i.

If the -i option is used, ntpd now looks for the configuration file
*before* it calls chroot().  Therefore, adjusting $ntpconf based on
the chroot value is wrong.

$ntpstep should be with $ntpconf; that is, outside of the chroot. 
Therefore, there is no need to pay attention to the -i option at all.

Comment 1 James Ralston 2004-12-15 00:47:25 UTC
Created attachment 108583 [details]
patch for /etc/rc.d/init.d/ntpd

This patch fixes all of the problems detailed in comment #1.

Comment 2 James Ralston 2004-12-15 00:48:52 UTC
Errr, the patch fixes all of the problems detailed in the initial bug
description, that is.

Comment 8 Red Hat Bugzilla 2006-08-10 18:24:39 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.