Bug 142926

Summary: multiple problems with ntpd init.d script
Product: Red Hat Enterprise Linux 4 Reporter: James Ralston <ralston>
Component: ntpAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0393 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 18:24:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 181409    
Attachments:
Description Flags
patch for /etc/rc.d/init.d/ntpd none

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.

http://rhn.redhat.com/errata/RHSA-2006-0393.html