Bug 4964

Summary: Linuxconf incorrectly sets up /etc/sysconfig/clock for apmd
Product: [Retired] Red Hat Linux Reporter: Yaron Minsky <yminsky>
Component: linuxconfAssignee: David Lawrence <dkl>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 6.0   
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-09-20 17:54:35 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 Yaron Minsky 1999-09-07 21:56:36 UTC 
When UTC is enabled, linuxconf sets up /etc/sysconfig/clock
such that the UTC line reads like this:

UTC="yes"

However, the file /etc/rc.d/init.d/apmd only tests if
UTC=true.   Thus, UTC is read as being false when it's set
to "yes".  This makes apmd screw up when it comes back up
and readjusts the clock.

I'm setting this to "high" severity because it seems like a
problem that must hit an enormous proportion of the people
using Redhat on a laptop.  And it's a real pain, and
possibly a critical problem for those people.
Comment 1 Yaron Minsky 1999-09-07 21:57:59 UTC 
I forgot to mention: This bug is closely related (I think) to bug
#3744
Comment 2 Michael K. Johnson 1999-09-20 17:54:59 UTC 
Fixed for RawHide and Red Hat Linux 6.1 in apmd-3.0beta9-3