deke@valhalla.ee.rochester.edu (08/04/88)
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." / \-----------------------------------------------------------------------------/
Mills@UDEL.EDU (08/04/88)
Deke, See RFC-1059. Then, you might want to talk to Mike Petry, who has a 4.3bsd daemon which is now chiming at a few dozen systems just now. Also, a bunch of new radio clocks have come up, making the total at least seven going on nine. Depending on your confidence and precision required, you might want to run NTP on only a few of your machines and timed on the rest; however, NTP depends for robustness on having a number of peers and using a weighted selection algorithm to cast out the falsetickers. Dave
CERF@A.ISI.EDU (08/04/88)
Deke, NTP RFC 1059 dated July 88 just released. RFC 1059 is an elective protocol and the RFC is in DRAFT STANDARD status. Vint Cerf