Bug 515
Summary: | Doing "hwclock --adjust" in rc.sysinit would be a good idea. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Göran Uddeborg <goeran> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | 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: | 2000-12-15 22:04:46 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
Göran Uddeborg
1998-12-18 12:35:16 UTC
This change request has been assigned to a developer for further review. I agree with this bug report. -Neal McBurnett fixed in initscripts-3.84. This was fixed. But in initscripts 5.49 the fix is gone again. Is this by design or by mistake? Design. We had it in place for a while, and there were many reports of it doing odd things with clocks. The current initscripts sets the hardware clock on shutdown as well as reading it on startup, so it should be kept relatively in sync. Ok. It won't be as good if the machine is only up for short times and then down for long. But if the other solution was causing other problems, I guess it's better than nothing. |