Bug 2422 - xntpd gets confused by suspend/resume
Summary: xntpd gets confused by suspend/resume
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xntp3   
(Show other bugs)
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-04-29 19:00 UTC by Marty Shannon
Modified: 2015-01-07 23:37 UTC (History)
1 user (show)

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.