Bug 7409 - apmd - date incorrect after resume
apmd - date incorrect after resume
Product: Red Hat Linux
Classification: Retired
Component: apmd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
Depends On:
  Show dependency treegraph
Reported: 1999-11-29 08:36 EST by gerald
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-29 12:08:14 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 gerald 1999-11-29 08:36:11 EST
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 12:08:59 EST
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.