Bug 2422

Summary: xntpd gets confused by suspend/resume
Product: [Retired] Red Hat Linux Reporter: Marty Shannon <martys>
Component: xntp3Assignee: Jay Turner <jturner>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-04-30 16:25:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marty Shannon 1999-04-29 19:00:42 UTC
Since xntpd doesn't run during suspend, a resume will cause
what appears to be a time difference that is too great to
correct by stepping, then it exits.

Comment 1 Jeff Johnson 1999-04-30 16:25:59 UTC
XNTP3 was never designed to work in apmd suspend/resume environments.
You might try running ntpdate -s periodically from cron which should
give you most of the benefits of XNTP w/o running xntpd.