Xref: utzoo comp.arch:3858 comp.dcom.lans:1110
Path: utzoo!mnetor!uunet!husc6!tut.cis.ohio-state.edu!bloom-beacon!gatech!udel!burdvax!bpa!cp1!sarin!wb3ffv!fallst!tkevans
From: tkevans@fallst.UUCP (Tim Evans)
Newsgroups: comp.arch,comp.dcom.lans
Subject: Re: Time synchronization in a Distributed Environment
Message-ID: <276@fallst.UUCP>
Date: 5 Mar 88 14:31:38 GMT
References: <druhi.2710> <1571@ogcvax.UUCP>
Organization: Tim Evans, Fallston, MD
Lines: 21
Summary: A hack to coordinate date/time among machines running Fusion (tm)

In article <1571@ogcvax.UUCP>, pase@ogcvax.UUCP (Douglas M. Pase) writes:
> In article <druhi.2710> aws@druhi.ATT.COM (SteereA) writes:
> Hi,
>   I am looking for articles, references, implementations,
> etc. for solving the problem of keeping N machines within
> a specified time of one another.  I appreciate any and all
> pointers.
> 
> 
In an environment where Fusion (tm) network software runs, you can hack a
way of coordinating date/time among a group of machines.  (This works in
Sys V, at least.)

Select one machine as a master, and manually keep its date/time correct.
Set up a cron on the rest (which must be run with root authority) that
executes the following command using Fusion's (tm) 'rx':

	date `rx machine_name date '+%m%d%H%M%y'`

While I don't know, other network software presumably has the ability
to remotely execute a command on another machine in the network.