Bug 7409 - apmd - date incorrect after resume
Summary: apmd - date incorrect after resume
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apmd   
(Show other bugs)
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-11-29 13:36 UTC by gerald
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-29 17:08:14 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 gerald 1999-11-29 13:36:11 UTC 
apmd assumes that the hw clock is set to GTM. If it is not, the date
is wrong after resume.

In addition the man page states that the "proxy command is searched for in
/etc/apmd/apmd_proxy". But apmd tries to execute /etc/apmd_proxy instead.
Comment 1 Bernhard Rosenkraenzer 1999-11-29 17:08:59 UTC 
Try the rawhide version - it eliminates the need for apmd_proxy and also gives
you the possibility to sync with the hardware clock (hwclock --hctosys) when
getting out of suspend mode.
Note You need to log in before you can comment on or make changes to this bug.