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: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: 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: ---

Description Göran Uddeborg 1998-12-18 12:35:16 UTC
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 21:29:59 UTC
This change request has been assigned to a developer for further
review.

Comment 2 nealmcb 1999-01-25 04:58:59 UTC
I agree with this bug report.
-Neal McBurnett

Comment 3 Bill Nottingham 1999-02-05 17:34:59 UTC
fixed in initscripts-3.84.

Comment 4 Göran Uddeborg 2000-12-15 21:56:15 UTC
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 22:04:42 UTC
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 19:26:25 UTC
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.