Hi Colin
Just had a look at the current version of ntp
02/22/1999 02:48AM 4,569,400 ntp-4.0.92c.tar.gz
Four and a half megs to do the job that I'm currently doing with
12k - no thanks :-))
This is one case of sledgehammer to crack a nut that I don't think is
really necessary in a hobby environment.
If someone else wants to do it then by all means - but they will still
have to solve the problem with mktime().
Robin. G8ECJ
----- Original Message -----
From: Colin Bradford <[EMAIL PROTECTED]>
To: Robin Gilks <[EMAIL PROTECTED]>; Richard Stearn
<[EMAIL PROTECTED]>
Cc: linux-hams list <[EMAIL PROTECTED]>
Sent: 29 March 1999 11:04
Subject: Re: Time bug
> >----- Original Message -----
> >From: Richard Stearn <[EMAIL PROTECTED]>
> >To: Robin Gilks <[EMAIL PROTECTED]>
> >Cc: <[EMAIL PROTECTED]>
> >Sent: 29 March 1999 01:19
> >Subject: Re: Time bug
> >
> >
> >> Robin
> >>
> >> Quick question while I look further into mktime. Why code your own
> daemon?
> >> NTP with a reference clock driver will do it all for you.
> >
> >How does this help get the time from an Oregon Scientific Rugby clock?
> >NTP is a protocol for getting the time from another machine - not for
> >reading data from the game (or other) port on a PC...
> >
>
>
> As I recall, the xntpd daemon for Unix supports many standard clock
sources,
> as well as ntp.
> So, you can use the code from xntpd, and modify it to suit your clock.
>
> Cheers,
>
> Colin.
>
>
