Bug 4964 - Linuxconf incorrectly sets up /etc/sysconfig/clock for apmd
Linuxconf incorrectly sets up /etc/sysconfig/clock for apmd
Status: CLOSED NEXTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-07 17:56 EDT by Yaron Minsky
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:
Environment:
Last Closed: 1999-09-20 13:54:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yaron Minsky 1999-09-07 17:56:36 EDT
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 17:57:59 EDT
I forgot to mention: This bug is closely related (I think) to bug
#3744
Comment 2 Michael K. Johnson 1999-09-20 13:54:59 EDT
Fixed for RawHide and Red Hat Linux 6.1 in apmd-3.0beta9-3

Note You need to log in before you can comment on or make changes to this bug.