Bug 515 - Doing "hwclock --adjust" in rc.sysinit would be a good idea.
Doing "hwclock --adjust" in rc.sysinit would be a good idea.
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
5.2
All Linux
low Severity low
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-12-18 07:35 EST by Göran Uddeborg
Modified: 2014-03-16 22:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-15 17:04:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Göran Uddeborg 1998-12-18 07:35:16 EST
According to the hwclock manual page:

It is good to do a hwclock --adjust just before the hwclock
--hctosys at system startup time ...

That makes sense.  Why not add that to rc.sysinit, if
/sbin/hwclock is found?
Comment 1 David Lawrence 1998-12-22 16:29:59 EST
This change request has been assigned to a developer for further
review.
Comment 2 nealmcb 1999-01-24 23:58:59 EST
I agree with this bug report.
-Neal McBurnett
Comment 3 Bill Nottingham 1999-02-05 12:34:59 EST
fixed in initscripts-3.84.
Comment 4 Göran Uddeborg 2000-12-15 16:56:15 EST
This was fixed. But in initscripts 5.49 the fix is gone again.  Is this by
design or by mistake?
Comment 5 Bill Nottingham 2000-12-15 17:04:42 EST
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.
Comment 6 Göran Uddeborg 2000-12-16 14:26:25 EST
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.

Note You need to log in before you can comment on or make changes to this bug.