Bug 146884

Summary: ntpd startup too early + hangs
Product: [Fedora] Fedora Reporter: Neal Becker <ndbecker2>
Component: ntpAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bjohnson, mattdm, suckfish
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-08 13:01:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neal Becker 2005-02-02 15:14:01 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
In FC3 ntpd has 2 problems

1) Starts too early
2) hangs

Especially if you want to use NetworkManager (which starts very late), ntpd
should be started later.

ntpd failing to start hangs the startup for about 10-15 seconds.  This
shouldn't happen.


Version-Release number of selected component (if applicable):
ntp-4.2.0.a.20040617-4


How reproducible:
Always

Steps to Reproduce:
1.boot w/ ntpd enabled without network connectivity or with changed connectivity
2.
3.
    

Additional info:

Comment 1 Ralph Loader 2006-01-13 05:40:58 UTC
I think if the call to the (deprecated) ntpdate in the init script were removed,
this (and several other) problems would disappear.

Instead, run ntpd with the -g flag to recover from large time errors.

Comment 2 Bernard Johnson 2006-02-10 23:31:28 UTC
This bug still exists even in rawhide.

As more and more people start to use NetworkManager, it's quite annoying to have
the delay of ntpd starting and then the error message because the network is not
started.

Comment 3 Matthew Miller 2006-07-10 21:38:38 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 4 Miroslav Lichvar 2006-07-27 13:00:56 UTC
system-config-date now doesn't fill the /etc/ntp/step-tickers file by default so
ntpdate isn't called during boot.

The issue with NetworkManager still needs to be addressed.

Comment 5 Miroslav Lichvar 2007-01-08 13:01:12 UTC
ntpd 4.2.4 handles dynamic interfaces correctly, so it should be finally ok with
NetworkManager.