🚀 go-pugleaf

>>>>> In article <1992Dec30.001810.21990@wuecl.wustl.edu>, heather@wuee1.wustl.edu (Heather A. Drury) writes:


heather> I am trying to get xntp to run on an SGI Indigo.  The daemon xntpd 
heather> exits right away, apparantly because "tickadj" and "tick" are not 
heather> used in the kernel.  Is there any way around this or am I out of luck?

Some time ago, I ported xntp (NTP V2) to the SGI platform. Patches are
available for anonymous FTP on sgigate.sgi.com, in the directory
~ftp/net-services/xntp. In addition is a compressed tar file
containing a set of binaries built with those patches. Since I'm an
SGI employee, I gotta give the full disclaimer (copied out of the
README file in that directory):

THIS CODE IS COMPLETELY UNSUPPORTED.

This software is provided without support and without any obligation on the
part of Silicon Graphics, Inc. to assist in its use, correction, modification 
or enhancement.  There is no guarantee that this software will be included 
in future software releases, and it probably will not be included.

THIS SOFTWARE IS PROVIDED "AS IS" WITH NO WARRANTIES OF ANY KIND INCLUDING THE
WARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULAR
PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.

Disclaimer disclaimer: I will, as my time permits, help you if you
have problems compiling or installing this software. I am also
interested in bug reports that apply to the SGI port. Please address
bugs/problems/questions to "scotth@sgi.com".


heather> Also, does anyone know if I can succesfully synchronize two Indigo 
heather> clocks running at 1200Hz to within 5 (or less) milliseconds, or am
heather> I dreaming?

We use a mix of xntpd and timed internal to SGI, and offsets are
mostly less than 30 msec. Most of these are not managed to minimize
offset (and in fact most are using timed off of an xntpd time master).
Especially with fast clocks on (and precision adjusted accordingly),
with careful tuning you could probably keep mostly 1-2 msec offsets
within a small group of hosts. Remember that default clock precision
is 10msec, the dispersions seen on the local net (I'm just checking as
I type) are on the order of one clock tick, or they are way off (hmm,
lots of hosts to check for missing time daemons....).

Good luck on your project!

=-=-=-=-=