Bug 58836 - ntp startup script falsely reports success on ntpdate sync failure
ntp startup script falsely reports success on ntpdate sync failure
Product: Red Hat Linux
Classification: Retired
Component: ntp (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-01-25 11:25 EST by Darren Gamble
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-28 03:59:43 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 Darren Gamble 2002-01-25 11:25:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
The startup script for ntp checks to see if /etc/ntp/step-tickers exists- if it 
does, it tries to run ntpdate to sync the clock.  However, the script reports 
success even if ntpdate fails

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

How reproducible:

Steps to Reproduce:
1. Change /etc/ntp/step-tickers to have an IP address of a server without ntp 
2. (Re)start ntpd with /etc/init.d/ntpd.

Actual Results:  Script reports success on ntpdate time sync.

Expected Results:  Script should have reported failure on ntpdate time sync.

Additional info:

This bug confused us for quite some time as to why ntpd was not working 
properly (considering the lack of good documentation on it- not even a man 
Comment 1 Harald Hoyer 2002-01-29 05:23:31 EST
fixed in 4.1.0b-5

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