[699] in linux-net channel archive
Re: Getting and setting time for client, how?
daemon@ATHENA.MIT.EDU (Michael Shields)
Sun Jul 16 10:17:34 1995
From: shields@tembel.org (Michael Shields)
To: jonathan@DSG.Stanford.EDU (Jonathan Stone)
Date: Sun, 16 Jul 1995 10:13:25 +0000 (GMT)
Cc: drew@poohsticks.org, linux-net@vger.rutgers.edu, GeisJ@rnd3.indy.tce.com,
torsten.duwe@informatik.uni-erlangen.de
In-Reply-To: <199507131251.FAA00666@Pescadero.Stanford.EDU> from "Jonathan Stone" at 1995-07-13 05:51:40
> I can appreciate the simplicity of using only one synchronization
> protocol on a network. Otherwise I don't see much point at all in
> using xntpd (NTP is capable of long-term synchronization down to
> microseconds) when one only has a 100hz-resolution interrupt-driven
> clock, and one also lacks Dave Mills' phase-locked-loop clock
> discipline, and the associated ntp_adjtime() call.
Actually, Linux used to have a kernel PLL, ported by Torsten Duwe.
However, it's not new enough for xntpd 3.4; Mills changed the interface
and Linux hasn't caught up. When I asked about this some time ago
Torsten said he was waiting for 1.3.
I'm cc'ing to him. What's the status now?
--
Shields.
