I designed a professional astronomical grade timebase that requires resync
every 48 days if it is programmed to have a millisecond stable resolution.
This mode has a predictable with a +/- 1 millisecond per day.
Andre Hedrick
The Linux IDE guy
On Sat, 9 Oct 1999, Stephen Williams wrote:
>
> mhw@wittsend.com said:
> > Xntpd keeps the system in sync by adjusting the clock and maintaining
> > information on it's rate of drift. This may not be so good if you are
> > on a dialup system, however.
>
> xntp includes ntpdate, which is similar to date but uses xntp servers.
> When I was dialup, I used ntpdate to resync my clock with a cron job
> and I got a good compromise of accurate time (including rate) and low
> re-dial rates. Twice a day may well be enough to keep pretty good time.
>
> BTW this is on an alpha.
>
> --
> Steve Williams "The woods are lovely, dark and deep.
> steve@icarus.com But I have promises to keep,
> steve@picturel.com and lines to code before I sleep,
> http://www.picturel.com And lines to code before I sleep."
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/