Red Hat Bugzilla – Bug 103736
/etc/localtime regeneration after modification of /etc/sysconfig/clock
Last modified: 2014-03-16 22:38:30 EDT
Description of problem: /etc/localtime never regenerated after changes were made to /etc/sysconfig/clock Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1.edit /etc/sysconfig/clock (changeing timezone for example.) Actual results: the date command returns the old timezone value even after reboot as it relies on /etc/localtime which is not updated at system boot. Expected results: /etc/localtime is regenerated based on the new /etc/sysconfig/clock settings Additional info:
It's regenerated when you use the included tools to modify /etc/sysconfig/clock; if *that's* not happening, that's a bug.
redhat-config-time doesn't allow for the selection of some timezones, like GMT and the likes. I think that a small modification to the initscripts to regenerate /etc/localtime on boot (or even on shutdown/reboot) would be a good thing.
Impossible to fix completely. It would need to be done before you set the time, and you don't necessarily have a /usr filesystem to copy *from* then.
Or before you're switching the machine off, during the shutdown.
In the case of manual modification of config files, it's the sysadmin responsibility to fix the consequences of such; I'm unwilling to start down the slippery slope of fixing them up afterwards in an automated fashion.