home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!udel!darwin.sura.net!ra!atkinson
- From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
- Newsgroups: dc.general
- Subject: Re: U.S. Naval Observatory and AtomClock
- Message-ID: <3568@ra.nrl.navy.mil>
- Date: 11 Sep 92 00:08:34 GMT
- References: <8574@hq.hq.af.mil> <1992Sep10.205412.16891@eco.twg.com>
- Sender: usenet@ra.nrl.navy.mil
- Followup-To: comp.protocols.time.ntp
- Distribution: dc
- Organization: Naval Research Laboratory, DC
- Lines: 23
-
- In article <1992Sep10.205412.16891@eco.twg.com> reece@eco.twg.com (Reece R. Pollack) writes:
-
- % Take a look at the NTP protocol before you start playing with the
- % daytime service. NTP will allow extremely accurate time
- % synchronization even across wide area networks. There are a couple of
- % NTP servers on the net which are synchronized by atomic clocks, and
- % quite a few synched to WWVB.
-
- Reece is quite correct. NTP is much more accurate than daytime or rdate
- or most anything else and NTP implementations are free. The specification
- for NTP is in several RFCs available online at various places (local to DC,
- try ftp.uu.net) via anonymous ftp.
-
- A list of known clocks on the Internet is in a file clocks.txt
- (spelling?) on louie.udel.edu and sources for an NTP daemon (xntp3)
- are also available there. Sundry other NTP stuff is there. There are
- very high quality clocks on the net local to DC. The USENET newsgroup
- comp.protocols.time.ntp is where discussion should head.
-
- Ran
- atkinson@itd.nrl.navy.mil
-
-
-