Bug 85944

Summary: ntp daemon not started on unconnected machines
Product: [Retired] Red Hat Linux Reporter: Reuben Thomas <rrt>
Component: ntpAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:09 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 Reuben Thomas 2003-03-11 09:45:40 UTC
Description of problem:

Before /etc/init.d/ntp starts up the ntp server, it tries to run ntpdate. If this fails, it doesn't start the server. Hence, on a machine that doesn't have a permanent internet connection (or more specifically, isn't connected at boot time), the daemon won't be run.

Version-Release number of selected component (if applicable):

4.1.1a

How reproducible:

Always

Steps to Reproduce:
1. Install ntp and activate it, then boot on a machine without a net connection
2.
3.
    
Actual results:

The "synchronizing with time server line" will say "failed" (correctly), and the daemon will not be started.

Expected results:

Immediate synchronisation should fail, but the daemon should still be started, so that when a net connection is made, the time server can be reached and used for synchronisation.

Additional info:

Comment 1 Harald Hoyer 2003-03-11 12:01:31 UTC
resolved in the latest rawhide versions... thx

*** This bug has been marked as a duplicate of 82200 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:09 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.