Bug 11020

Summary: Hardware clock not adjusted for skew.
Product: [Retired] Red Hat Linux Reporter: Sam Varshavchik <mrsam>
Component: xntp3Assignee: Jeff Johnson <jbj>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 6.2CC: dr
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-05-05 18:04:12 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 Sam Varshavchik 2000-04-24 22:50:12 UTC 
I find that xntp does not adjust the realtime hardware BIOS clock, only the
system clock.  Over time, if a significant skew builds up, on the next
reboot the clock will be thrown back.

If the master is rebooted, when there's a skew, all the slaves will get
their clocks reset.  If the slave is rebooted, several minutes will go by,
then the slave's clock will be jump by a large amount, when it is
resynchronized with a master.

Solution:  add the following to /etc/rc.d/init.d/xntpd, after the killproc
that stops the daemon:

   /sbin/hwclock --systohc

This will adjust the hardware clock with the accumulated skew, before the
system shutdown.
Comment 1 Daniel Roesen 2000-04-27 06:18:59 UTC 
xntpd should update the RTC itself. Are you running on Compaq ProLiant hardware?
I think i noticed this problem on ProLiants (hwclock --systohc being unable to
update the RTC).
Comment 2 Jeff Johnson 2000-05-05 18:04:59 UTC 
*** This bug has been marked as a duplicate of 1142 ***