Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!husc6!sri-unix!teknowledge-vaxc!dplatt
From: dplatt@teknowledge-vaxc.ARPA (Dave Platt)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Using `navclock' to set time (was: `Re: Time sync on Suns')
Message-ID: <12710@teknowledge-vaxc.ARPA>
Date: Wed, 13-May-87 13:36:11 EDT
Article-I.D.: teknowle.12710
Posted: Wed May 13 13:36:11 1987
Date-Received: Sat, 16-May-87 04:15:18 EDT
References: <11893@teknowledge-vaxc.ARPA> <750@mcgill-vision.UUCP> <3737@elroy.Jpl.Nasa.Gov> <183@vianet.UUCP>
Distribution: na
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 19
Xref: mnetor comp.unix.questions:2290 comp.unix.wizards:2297
In-reply-to: devine@vianet.UUCP's message of 13 May 87 00:04:23 GMT

Posting-Front-End: GNU Emacs 18.41.3 of Tue Apr  7 1987 on teknowledge-vaxc (berkeley-unix)


Another (possibly less-expensive) source for a time-check signal can
is the U.S. Naval Observatory at (900) 410-TIME [410-8463 for those
without letters on their dials/pads].  This costs $.50 for the first
minute and $.35 for each minute thereafter (the last time I
checked...).  I seem to recall reading that this service is
implemented using some sort of special phone lines that ensure a
minimum delay between the sender and the receiver (presumably there
are no geostationary-satellite links involved).  Also, it's capable
of accepting a very large number of calls at once (over a thousand, I
believe) so you're unlikely to encounter a busy signal.

This number may be available only over AT&T lines... if you have a
different long-distance carrier, and receive a "no such number"
recording when you dial, try dialing 10288 first to force the call to
be sent over AT&T.

Disclaimer: I don't work for AT&T;  I do own a few shares of AT&T
stock but probably won't get rich from the dividends of any 900-area
calls you may happen to make...