Xref: utzoo comp.dcom.lans:1663 comp.protocols.tcp-ip:4253
Path: utzoo!utgpu!attcan!uunet!husc6!mailrus!cornell!rochester!ur-tut!ur-valhalla!deke
From: deke@valhalla.ee.rochester.edu
Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip
Subject: Status of NTP?
Keywords: NTP
Message-ID: <1402@valhalla.ee.rochester.edu>
Date: 3 Aug 88 17:29:04 GMT
Sender: usenet@valhalla.ee.rochester.edu
Reply-To: deke@ee.rochester.edu (Deke Kassabian)
Organization: URochester Department of Electrical Engineering
Lines: 16


What is the status of NTP?  I have rfc958, is this the most (and
only) relevant document?

I would like to keep 35 or so machines on my networks time-synched
*with eachother*..... having that common time be "correct" is
icing on the cake.  Up till now I have tried using 4.[23]BSD timed
and /usr/ucb/rdate on UN*X machines, and they work fine, but I
certainly wouldn't mind using a more elegant method.


- Deke Kassabian
-------------------------------------------------------------------------------
\ deke@ee.rochester.edu                  "Experience is something you don't   /
\   or ...!rochester!ur-valhalla!deke     get until just after you need it."  /
\-----------------------------------------------------------------------------/