Bug 7409

Summary: apmd - date incorrect after resume
Product: [Retired] Red Hat Linux Reporter: gerald
Component: apmdAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
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: --- Target Upstream Version:
Embargoed:

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.