From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 Description of problem: When the NTP option is checked in dateconfig's GUI, and a server is entered, the tool appropriately adds the "server" entry for that given hostname, but fails to add a "restrict" entry for that same hostname. Given the default config that comes with the latest package for NTP, which includes a "restrict default ignore", a "restrict" definitely needs to be added for the synchronization to occur. In it's current state, dateconfig fails to successfully configure the specified NTP server. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Run dateconfig 2. Enter appropriate settings and OK it 3. Check /etc/ntp.conf... no "restrict" entry for the specified server Actual Results: Either by looking at the logfile, or doing a "ntpdc localhost" followed by a "peers" command, or finally by running "ntpd -ddd", it's very clear, especially in the latter, that ntpd is dropping the response due to ACL restrictions Expected Results: ntpd should have accepted the repsonse from the NTP server and start synching itself to that server Additional info:
Happens here too
Please try redhat-config-date-1.4-7 out of Rawhide
*** This bug has been marked as a duplicate of 70557 ***