[comp.protocols.time.ntp] confused newcomer asks stupid questions.

billd@fps.com (Bill Davidson) (04/27/91)

I've spent a lot of time with the various documents (man pages, RFC,
other ps documents that came with the software) and I'm still confused,
so I appeal to the net.

First, my situation:

I am not on the Internet.

I do not have a spiffy radio reference clock and I probably won't get
one.

Time accuracy is not that important to me.  What is important is that
all the machines on my network be synchronized.  Being a minute or so
off of what the Bureau of Standards (or whatever they call themselves
these days) thinks the time is is no big deal to me.  Having one
machine on my network think that it's one time and another machine
think it's a minute later is potentially a serious problem.

For my BSD machines, timed has served my needs well.  Right now, on the
SparcStations, I run a script out of cron every so often that does an
rdate to one of the machines running timed (there are 10 machines
running timed and collectively they show suprisingly low amounts of
drift).  This is a hack at best and I'd really prefer to do something a
little more standard.

Now I have a bunch of SparcStations running SunOS 4.1 and 4.1.1 (no
timed).

I got my source off of trantor.umd.edu (ntp-test.tar May 1989).  Is
this the most current version?

How should I set up my ntp.conf files on them to keep them
synchronized?  I'm beginning to think it'd be better to just port
timed.

--Bill Davidson (billd@fps.com)
-- 
The great thing about Alzheimer's that is you meet new people every day.