[712] in linux-net channel archive
Re: Getting and setting time for client, how?
daemon@ATHENA.MIT.EDU (Torsten Duwe (Emacs))
Mon Jul 17 21:25:39 1995
From: Torsten Duwe (Emacs) <duwe@immd4.informatik.uni-erlangen.de>
Date: Mon, 17 Jul 1995 18:42:21 GMT
To: shields@tembel.org (Michael Shields)
Cc: jonathan@DSG.Stanford.EDU (Jonathan Stone), drew@poohsticks.org,
linux-net@vger.rutgers.edu, GeisJ@rnd3.indy.tce.com,
rfflaxa@immd4.informatik.uni-erlangen.de,
snprobst@immd4.informatik.uni-erlangen.de
In-Reply-To: <m0sXQhV-000DYhC@yage.tembel.org>
>>>>> "Michael" == Michael Shields <shields@tembel.org> writes:
>> 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.
Don't worry about that - the daemon will keep track of all the necessary
parameters then instead of the kernel. You don't have the ultimate precision
but you'll be at about 1ms if your source is good.
Michael> Actually, Linux used to have a kernel PLL, ported by Torsten
Michael> Duwe. However, it's not new enough for xntpd 3.4; Mills changed
Michael> the interface and Linux hasn't caught up. When I asked about
Michael> this some time ago Torsten said he was waiting for 1.3.
Michael> I'm cc'ing to him. What's the status now? -- Shields.
(did I tell you this before ?) I promised to supply a working Kernel PLL for
our LST 2.1 Erlangen distribution, which goes to beta RSN. My workload has
increased even more this month, but I reserve a little time during
weekends. count on that or next month (or 2 weeks if you want ... :-)
Torsten
