Bug 80473 - Drift file for NTP support wrong.
Drift file for NTP support wrong.
Status: CLOSED DUPLICATE of bug 66136
Product: Red Hat Linux
Classification: Retired
Component: dhcpcd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Depends On:
  Show dependency treegraph
Reported: 2002-12-26 19:42 EST by bryan
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description bryan 2002-12-26 19:42:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:
Gecko/20020508 Netscape6/6.2.3

Description of problem:
As a security fix for NTP, the daemon wishes to own the directory in which the
drift file is placed.  The drift file as create by dhcpcd is /etc/ntp.drift. 
NTP prefers something like /etc/ntp/drift where /etc/ntp can be owned by ntp.

This interaction of two products is unfortunate but the problem truly lies with
dhcpcd rather than ntp since dhcpcd creates the file name and provides no method
for altering the name short of editting the source for dhcpcd.  I have made this
change to the sources and ntp correctly starts for me.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure system to "Automatically obtain IP address settings with: dhcp
2. Configure dhcp server to offer NTP server "option ntp-servers"


Actual Results:  dhcpcd writes /etc/ntp.conf file with driftfile entry
/etc/ntp.drift and
ntpd fails to start.

Expected Results:  dhcpcd should write /etc/ntp.conf file with driftfile entry

Additional info:

The added security for ntpd is admirable but it should be synced with dhcpcd...
Comment 1 bryan 2003-01-03 13:09:03 EST
Sorry I didn't do the correct search so I missed this previous resolution.

*** This bug has been marked as a duplicate of 66136 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:36 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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