Bug 103736
| Summary: | /etc/localtime regeneration after modification of /etc/sysconfig/clock | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Roger Nunn <rnunn> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | CC: | bnocera, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-09-05 16:24:07 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: | |||
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. |
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: