Bug 6185

Summary: /usr/sbin/setclock handles UTC/ARC incorrectly
Product: [Retired] Red Hat Linux Reporter: chris
Component: timeconfigAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: chris
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-10-21 17:42:34 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 chris 1999-10-21 13:31:29 UTC 
The version of /usr/sbin/setclock distributed with RedHat
6.1 (timeconfig-3.0-5) interprets the values in
/etc/sysconfig/clock slightly differently from the rest of
the system.  Whereas /etc/rc.d/rc.sysinit checks whether the
variables $UTC or $ARC are set to "yes" or "true",
/usr/sbin/setclock only checks for the value "true".

This problem is compounded by the fact that the RH install
process sets $UTC to "yes" in /etc/sysconfig/clock (if a UTC
hardware clock is requested).  So the default install will
read the value from the hardware clock at system startup as
UTC, but when /usr/sbin/setclock is used to reset the
hardware clock it may fail to use UTC.
Comment 1 Bill Nottingham 1999-10-21 17:42:59 UTC 
Fixed in timeconfig-3.0.1-1.