Red Hat Bugzilla – Bug 1006248
/etc/sysconfig/clock does nothing
Last modified: 2014-01-02 12:30:58 EST
Description of problem:
/etc/sysconfig/clock is not accessed during boot. The file does nothing. It's confusing, and should either be removed or replaced with some documentation.
Version-Release number of selected component (if applicable):
I chose "basesystem" because I can't find any more suitable component.
$ rpm -qf /etc/sysconfig/clock
file /etc/sysconfig/clock is not owned by any package
... but it seems to exist on all RHEL6-machines I've checked at (as well as some derivative distributions).
Steps to Reproduce:
0. grep -r /etc/sysconfig/clock /etc/rc* /etc/init.d
1. Make sure atime is turned on the root file system
3. stat /etc/sysconfig/clock
* No references to /etc/sysconfig/clock when grepping for it
* /etc/sysconfig/clock is not accessed during boot
File should be referenced from one of the init scripts, it should be accessed during boot, or it shouldn't exist at all if it's obsoleted.
I got told that although /etc/sysconfig/clock is not used by RHEL, there may be legacy applications depending on this one, notably tomcat - http://grokbase.com/t/tomcat/users/051m0s38p2/how-to-change-the-timezone-for-tomcat#20050120zlgufj6cgdsma7i2olrgcpwia4 - although on my RHEL/Tomcat hosts /etc/localtime seems to be respected.
If the file has to exist for backward-compatibility with legacy apps, I suggest to at least add a comment of explanation in the file.
Thanks for report, basesystem is definitely wrong, use distribution component when you are not sure what is responsible for this. In that case, AFAIK anaconda is creating the file, reassigning there.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Thanks for the bug report. We have removed writing out this file from later versions of anaconda, so this will be fixed in RHEL-7. See bug 859217. If you require this fix in an update release of RHEL-6, please go through your support representation who will raise the issue for planning purposes. Thanks again.