Bug 84028
| Summary: | redhat-config-date has issues with UTC=1 in /etc/sysconfig/clock | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Brian "netdragon" Bober <netdragon> |
| Component: | redhat-config-date | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | ||
| 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: | 2006-02-21 18:51:42 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: | |||
The latest redhat-config-date in Rawhide should handle the UTC and ARC fields correctly. This is basically a duplicate of bug #72149 *** This bug has been marked as a duplicate of 72149 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
Description of problem: Here was what my /etc/sysconfig/clock had because of redhat-config-date: redhat-config-date doesn't recognize UTC=1 though... So it Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Edit /etc/sysconfig/clock to this: ZONE="America/New_York" UTC=true ARC=0 2. run redhat-config-date (Use UTC should be checked) and then just click "OK" 3. /etc/sysconfig/clock is now: ZONE="America/New_York" UTC=1 ARC=0 4. run redhat-config-date again and its no longer checked because redhat-config-date doesn't recognize the value it set itself (UTC=1). Actual results: redhat-config-date sets UTC=1 into /etc/sysconfig/clock but doesn't recognize it. Expected results: redhat-config-date sets it to UTC=true Additional info: Also note that the time applet in Gnome 2 on RH8.0 becomes incorrect if you enable UTC in its prefs. Don't know if that's related.