Bug 7409 – apmd - date incorrect after resume

Bug 7409 - apmd - date incorrect after resume

Summary:	apmd - date incorrect after resume

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	apmd (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-11-29 08:36 EST by gerald
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

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

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