Bug 79772 - redhat-config-date does not update /etc/localtime and /etc/sysconfig/clock
redhat-config-date does not update /etc/localtime and /etc/sysconfig/clock
Status: CLOSED DUPLICATE of bug 72149
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-date (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Depends On:
  Show dependency treegraph
Reported: 2002-12-16 15:02 EST by Roberto Scaramuzzi
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:50:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Roberto Scaramuzzi 2002-12-16 15:02:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
redhat-config-date does not update /etc/localtime and /etc/sysconfig/clock

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1. start KDE as a regular user
2. access redhat-config-date, either from the Start Here item on the desktop or
by right-clicking on the clock applet in the taskbar
3. change timezone

Actual Results:  The timezone stayed the same. Rebooting did not help.

Expected Results:  The timezone should have been reset to the new values

Additional info:

The files /etc/sysconfig/clock and /etc/localtime were not updated (this may be
a permission problem or a bug in the scripts)

I fixed the problem by manually editing /etc/sysconfig/clock and by copying the
appropriate file in /usr/share/timezone to /etc/localtime

This is obviously beyond the capabilities of the normal user.
Comment 1 Brent Fox 2002-12-17 12:37:54 EST

*** This bug has been marked as a duplicate of 72149 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:22 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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