Bug 79400
Summary: | redhat-config-date fails to launch | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Nick Dimiduk <dimiduk.1> |
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: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-12-11 09:46:55 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: |
Description
Nick Dimiduk
2002-12-11 09:43:23 UTC
Oops... to update my last comment: the system time is set at boot after connecting to a time server. The resulting system time is set 14 hours ahead of local time... GMT +9 I believe. Sorry for the confusion. -nd The contents of the /etc/sysconfig/clock file must have changed. I don't think that the motherboard change affected this. This bug report is a duplicate of bug 76313, so I'm going to close it as a dupe. However, you can still respond to this bug report and I'll try to help you out. Can you post the contents of your /etc/sysconfig/clock file? I think what has happened is that a timezone that redhat-config-date doesn't understand has been set in the /etc/sysconfig/clock file. *** This bug has been marked as a duplicate of 76313 *** |