Xref: utzoo comp.unix.admin:1968 comp.unix.questions:31654
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!uw-beaver!ssc-vax!bcsaic!vince
From: vince@bcsaic.UUCP (Vince Skahan)
Newsgroups: comp.unix.admin,comp.unix.questions
Subject: Re: syncronizing clocks on workstations
Message-ID: <47897@bcsaic.UUCP>
Date: 24 May 91 15:47:44 GMT
References: <1991May21.175317.12255@Citicorp.COM> <1991May21.201152.9655@cis.ohio-state.edu> <1991May23.014145.212@wizard.uucp>
Organization: Boeing Aerospace and Electronics - Seattle
Lines: 24

In article <1991May23.014145.212@wizard.uucp> bob@wizard.uucp (Bob Smith) writes:
>In <1991May21.201152.9655@cis.ohio-state.edu> george@news.cis.ohio-state.edu (George M. Jones) writes:
>
>> pdesh@Citicorp.COM (Peter Deshpande) writes:
>>     
>>     Does anyone know a way to syncronize clocks on a network involving
>>     many (sun) workstations and servers?

I wrote a shell script that runs out of cron on one workstation with the
master (by definition..."good") clock and goes out and does a 
rsh $system date xxxxxxxx command.  It works pretty well in practice if
you have one "group of systems" with the ability for root to do rsh's
among systems in the group.

let me know if you want a copy. It keeps my 75 systems to about 1 second
either way.

I've used "timed" on Apollos which also worked pretty well, but creates
a measurable (but maybe insignificant) load on the systems.
-- 
----------------------------------------------------------------
                         Vince Skahan   
 vince@atc.boeing.com                  ...uw-beaver!bcsaic!vince
        	(lifelong Phillies fan...pity me)