Bug 130121 - Incorrect description of settings for HWCLOCK in /etc/sysconfig/clock
Summary: Incorrect description of settings for HWCLOCK in /etc/sysconfig/clock
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Minor
Target Milestone: ---
Assignee: Ruediger Oertel
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-21 22:36 UTC by Stephan Wefing
Modified: 2005-10-25 21:03 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Wefing 2005-10-21 22:36:09 UTC 
The comment above the HWCLOCK entry in /etc/sysconfig/clock reads:

# Set to "-u" if your system clock is set to GMT, otherwise "".

However, even for localtime, HWCLOCK should always be set to "--localtime". This
is due to the fact that without specifying the time type, the type that was
"active" at the last change of the hardware clock will remain the "active" type,
see "man hwclock" (the current type is stored in /etc/adjtime). Hence, changing
from UTC to local time by changing "-u" to "" may not work.
Comment 1 Ruediger Oertel 2005-10-25 15:36:35 UTC 
that comment has been reading:
# Set to "-u" if your system clock is set to UTC, and to "--localtime"
# if your clock runs that way.
for quite a while already.
Comment 2 Stephan Wefing 2005-10-25 21:03:18 UTC 
Hmmm, may be that the effect depends on what is going on during an update? I checked /etc/sysconfig/clock on three different systems: one has been updated several times starting with SuSE 5.3 (now SuSE 10.0), one has been updated starting with SuSE 6.3 (now SuSE 9.0), and on the last one SuSE 9.2 has been installed from scratch. On the first two systems, the "--localtime" is missing in the comment, whereas it is present on the last system. In addition, there is an entry DEFAULT_TIMEZONE in /etc/sysconfig/clock of the third system which is missing in the other systems.