home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.time.ntp
- Path: sparky!uunet!shearson.com!snark!pmetzger
- From: pmetzger@snark.shearson.com (Perry E. Metzger)
- Subject: Re: xntpd and timed, etc
- Message-ID: <1992Dec23.015924.19111@shearson.com>
- Sender: news@shearson.com (News)
- Organization: /usr/local/lib/news/organization
- References: <1992Dec17.145434.199386@ipgaix.unipg.it> <1992Dec18.175438.16954@Arco.COM> <BzH0IM.2Bx@ra.nrl.navy.mil>
- Distribution: na
- Date: Wed, 23 Dec 1992 01:59:24 GMT
- Lines: 22
-
- atkinson@itd.nrl.navy.mil (Randall Atkinson) writes:
- > NTP version 1 is really old. They should upgrade from using ntpd(8)
- >to using xntpd(8) using the freely distributable sources available via
- >anonymous ftp from /pub/ntp on louie.udel.edu (the official xntp3
- >archive site).
-
- Its hard for people who need the code to work as advertised to do
- this. I'm one of those poor schlubs out there who actually needs to
- use a particular machine's internal clock as a master because we don't
- have a radio clock or a suitable direct internet connection --
- instead, I sync certain machines every few hours to NIST by phone.
- This isn't perfect, but getting my machines synced to each other is
- more important than getting them to within milliseconds of real time;
- a fiftieth of a second off the world (what I get in practice) is fine.
- Unfortunately, xntp3 has a bug that prevents the local clock as time
- source option from working, and no one out there seems to have a fix.
- Thus, I can't use xntp3, in spite of the fact that I'd like to.
-
- --
- Perry Metzger pmetzger@shearson.com
- --
- Laissez faire, laissez passer. Le monde va de lui meme.
-