Red Hat Bugzilla – Bug 129513
ntp configuration on first startup need to be online
Last modified: 2007-11-30 17:10:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040625
Description of problem:
If you choose to use "ntp" during the "firstboot" procedure and you
click on the "next" button, if you're not connected to the network you
cannot continue because ntp doesn't find his server.
In this way you have to deactivate ntp for continue the setup process.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC3-test1 (with firstboot package)
2. On the ntp setup of firstboot choose to use it
3. Disconnect from the network
4. press "next" button
Actual Results: ntp doesn't connect to the ntp server so you can't
continue with the firstboot setup
Expected Results: a message that inform you of the network problem
but it let you to continue
system-config-date shows that screen, so it needs to detect networking there
and decide to show ntp or not.
Not sure whether this can be done (sensibly) in s-c-date. If ntpd could
determine whether it can reach name-/timeservers before trying to do that (and
timing out) it would be a start, but that would still leave the issue of
communicating that back to s-c-date...
Removing block on FC3, FC4 target trackers.
Current s-c-date in Rawhide actually checks whether NTP hosts are reachable or
not (gives a warning in that case). Unless someone tells me differently, I
consider this closed.