Bug 85944 - ntp daemon not started on unconnected machines
ntp daemon not started on unconnected machines
Status: CLOSED DUPLICATE of bug 82200
Product: Red Hat Linux
Classification: Retired
Component: ntp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-03-11 04:45 EST by Reuben Thomas
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Reuben Thomas 2003-03-11 04:45:40 EST
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):


How reproducible:


Steps to Reproduce:
1. Install ntp and activate it, then boot on a machine without a net connection
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 07:01:31 EST
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 13:52:09 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.