Red Hat Bugzilla – Bug 217663
ntp update resets "Synchronize system clock" flag
Last modified: 2008-01-11 16:03:32 EST
Description of problem: I generally bring up my network after I boot my laptop. I like to use ntp, but I don't want it to do the initial "ntpdate" on boot because it'll always fail, so I un-check the "Synchronize system clock before starting service" flag in system-config-time. But every time there's a new version of ntp (as there was yesterday), that flag gets reset and I get an ugly "FAILED" on boot again until I rerun the configuration and uncheck it again. Version-Release number of selected component (if applicable): ntp-4.2.2p4-2.fc6 How reproducible: Always Steps to Reproduce: 1. Run system-config-time and uncheck the "Synchronize system clock before starting service" advanced option 2. Update to a new version of ntp Actual results: Checkbox is checked again Expected results: Checkbox should stay unchecked
Hmm, weird. The ntp package has empty /etc/ntp/step-tickers file, the update of ntp package shouldn't replace the empty file with something. What is the content of the file?
Aha! Thanks for that; it's a bit clearer what might be going on. Here's /etc/ntp/step-tickers: ===== 129.215.216.248 129.215.202.253 ===== Here's /etc/ntp/step-tickers.predhclient: ===== ===== (yes, an empty file) The two IP addresses in the above are local NTP servers that, I suspect, are provided by the DHCP server at work where I plug in my laptop. Is this somehow interacting with the ntp configuration?
Ok, dhclient is replacing the file.
I've fixed this problem and prepared an update for FC-6. The new package is dhcp-3.0.5-1.fc6. It's currently available in the testing updates repository. Please test it out and let me know if it works so I can move it to final update status: http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/
Well, FC-6 is now end of life. This fix has been incorporated in to both Fedora 7 and Fedora 8 as well as rawhide.