Path: utzoo!utgpu!trantor.umd.edu!ntp-relay
Message-ID: <9002280049.AA10654@intrepid.itstd.sri.com>
To:	bob@kahala.soest.hawaii.edu (Bob Cunningham)
Cc:	ntp@trantor.umd.edu
Subject: Re: clock driver? 
References: Your message of Tue, 27 Feb 90 14:28:18 K.
Date:	Tue, 27 Feb 90 19:49:05 EST
From:	davy@itstd.sri.com
Newsgroups: list.ntp
Distribution: ut
Approved: devnull@gpu.utcs.toronto.edu


     From:  bob@kahala.soest.hawaii.edu (Bob Cunningham)
     Date:  Tue, 27 Feb 90 14:28:18 HST
     Subject:  Re: clock driver?

     Just sent you the source for read_tt468.c (for ntpd).  Check the format
     of the input it expects (which is that of a GOES clock) and if it's
     like what the 60-DC uses you might be able to use it.  If not, then
     perhaps there's enough similarity that you might be able to use it as a
     template for your own code.  You'll want to check both the exact format
     assumed to be provided by the clock as well as how "quality" is handled
     (which I'd guess might be considerably different).

Got it, many thanks.  Taking a quick pass through the code, it looks like
making it work with my clock should be fairly simple.  The output format
of the 60-DC is the same as the 468-DC, except the 60-DC has a "format"
command which lets me turn on milliseconds, i.e.:

	<SOA>DDD HH:MM:SS.sssQ

I don't know whether this is worth having or not; again, if anyone has
experience in these things, I'd appreciate advice.

     To actually use it, you'll need to fiddle with ntpd.c and Makefile a bit.
     I'll be glad to supply the simple diffs I use for those to get read_tt468
     working if you like.

Sure, I'd appreciate them if you've got the time.

Hopefully, at this rate, we'll be "on the air" as a stratum 1 server in only
a week or two (depending on how long I test it for :-).

--Dave