+++ This bug was initially created as a clone of Bug #139715 +++ Description of problem: If DHCP provides the NTP server, dhclient-script generates ntp.conf but uses "authenticate yes" which ntp-4.2.0.a.20040617-4 dislikes as /var/log/messages shows: Nov 17 19:11:37 host ntpd[4047]: configure: keyword "authenticate" unknown, line ignored Version-Release number of selected component (if applicable): dhclient-3.0.1-11 How reproducible: Always. Steps to Reproduce: 1. Configure DHCP server to send NTP server option. 2. Boot client 3. Observe generated ntp.conf and the complaint in /var/log/messages. Actual results: As above. Expected results: A valid configuration. Additional info: By the way, rpm -qf shows /sbin/dhclient-script as belonging to dhclient, but there is no dhclient component for Fedora Core 3 in this Bugzilla ? -- Additional comment from dbolcioni on 2004-11-17 13:30 EST -- Please note that I do not believe this is a duplicate of the various earlier problems with ntp.conf documented in Bugzilla; I bothered with a quick check. It seems that "authenticate yes" is no longer liked by ntp, although it used to be fine. -- Additional comment from jvdias on 2004-11-17 16:17 EST -- The dhclient-script was overwriting the /etc/ntp.conf and /etc/ntp/step-tickers files when it received new ntp servers from the DHCP server. With dhcp-3.0.1-14, DHCP now merges in only the new servers with the existing ntp.conf contents, so other non-server configuration is preserved. dhcp-3.0.1-14 will be available from tomorrow in the Fedora Development (rawhide) repository, and from : http://people.redhat.com/~jvdias/DHCP/FC3/ Please test dhcp-3.0.1-14 and let me know how it works - then if it works ok I'll push it to FC3 updates.
fixed with dhcp-3.0.1-40_EL4
fixed with dhcp-3.0.1-40_EL4+
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/RHBA-2006-0114.html