Bug 117779 - Dhclient presets bad driftfile location
Summary: Dhclient presets bad driftfile location
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: dhcpcd   
(Show other bugs)
Version: 3.0
Hardware: All Linux
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-03-08 14:35 UTC by Thomas Sippel - Dau
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-11 15:50:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:566 normal SHIPPED_LIVE Updated dhcp and dhclient packages 2005-05-26 04:00:00 UTC

Description Thomas Sippel - Dau 2004-03-08 14:35:46 UTC
Description of problem: 
If a RedHat Enterpse Linux 3 Workstation is configured to  
acquire IP address with dhclient, and the dhcp server provides  
a set of ntp servers in response, and there is no /etc/ntp.conf file,  
the dhclient script (/sbin/dhclient-script) presets a driftfile  
/etc/ntp/data/drift. As the ntp data directory has been moved  
to /var/lib/ntp, this creates frequent messages as the directory  
/etc/ntp/data is no longer created.  
Version-Release number of selected component (if applicable):  
How reproducible:Clear from Source code  
Steps to Reproduce:  
1.Review Source  
Actual results:  
Frequent messages in /var/log/messages  
Expected results:  
Maintenance of driftfile in proper location  
Additional info:

Comment 1 Daniel Walsh 2004-03-25 18:23:33 UTC
fixed in dhcp-3.0pl2-6.16 and above.

Comment 2 John Flanagan 2004-12-21 19:42:05 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.