[Dxspider-support] Setting System HW Clock

[Bob Nielsen]

Bill,

Typically the synchronization is done at startup and shutdown by an
init.d script invoking hwclock, however chrony has the ability to adjust
the hardware clock as well as the system clock to NTP standards (I use
chrony but without invoking this feature, as it appears to be a bit
messy).

Bob, N7XY

On Tue, Dec 14, 2004 at 03:33:21PM -0800, Bill Shell wrote:
> Mike,
> 
> I guess what I never saw work was ntpd or xntpd synchronizing the hardware
> clock to the system clock.  It must be the magic worked by one of those
> switches I never investigated.  Hi Hi.  Is your synchronization of the
> hardware clock accomplished by a switch or is in the shutdown script in
> /etc/init.d ?
> 
> xntpd was the daemon I was using to keep the system times synchronized with
> Internet time.  The error file with time delta was recorded in a file, but
> it didn't change my hardware clock.  The only changes I made to the basic
> RedHat and SuSE installations were to change the .conf file to point to an
> Internet time server.  
> 
> TU es 73,
> Bill
> 
> 
> -----Original Message-----
> From: dxspider-support-bounces at dxcluster.org
> [mailto:dxspider-support-bounces at dxcluster.org] On Behalf Of Mike McCarthy,
> W1NR
> Sent: Tuesday, December 14, 2004 10:08 AM
> To: n6ws at charter.net; The DXSpider Support list
> Subject: RE: [Dxspider-support] Setting System HW Clock
> 
> 
> I run ntpd and it keeps the clock within a few milliseconds of NIST at all
> times.  One of the last things that happens in the shutdown phase (verified
> by the console log) is the message "Syncing hardware clock with system
> time".
> 
> For Windows, I use Tardis from http://www.kaska.demon.co.uk/.  This one also
> sets the HW clock as it is running.
> 
> Each of these run in the background and constantly update the system time.
> In the case of Tardis, it even reports how much clock drift you have in the
> HW clock.
> 
> Mike, W1NR
> 
> 
> -----Original Message-----
> From: dxspider-support-bounces at dxcluster.org
> [mailto:dxspider-support-bounces at dxcluster.org]On Behalf Of Bill Shell
> Sent: Tuesday, December 14, 2004 12:41 PM
> To: 'The DXSpider Support list'
> Subject: [Dxspider-support] Setting System HW Clock
> 
> 
> Hello All,
> 
> This may be a little off-topic for those with local Linux systems or Windows
> systems, but...
> 
> I have had a problem with the hardware clock drifting on a few of the remote
> systems I administer.  I was keeping the system time accurate by
> synchronizing with Internet time, but on a system restart the time would
> revert back to the hardware clock time.  I was not aware I could set the
> hardware clock until I came across this article in the Linux Gazette:
> http://linuxgazette.net/108/park1.html
> 
> I have now made similar routines that daily set the system time to Internet
> time and then sync the hardware clock to the system time.  This fixed the
> problem of having the hardware clock set the system time incorrectly on
> startup.  This is particularly helpful since the three of the DXSpider
> systems are about 160 miles away and a fourth system is about 70 miles away.
> 
> I hope this information can help anyone having a similar problem.  If anyone
> needs specific information, please don't hesitate to ask.
> 
> 73, Bill
> N6WS
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://www.tobit.co.uk/mailman/listinfo/dxspider-support
> 
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at dxcluster.org
> http://www.tobit.co.uk/mailman/listinfo/dxspider-support
> 
> 

-- 
Bob Nielsen, N7XY                          n7xy (at) n7xy.net
Bainbridge Island, WA                      http://www.n7xy.net