On Sun, Jan 02, 2000 at 01:41:08AM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Rodney W. Grimes" writes
> :
>
> >Does it help in the 3.4-stable version to set the second value in ntpdrift
> >to 1?
>
> Yes, although I have never checked all the boundary conditions
> to make sure the kernel-pll is stable over the entire envelope.
>
> I'm doing that for the NTPv4/nanokernel combo, and I'm resolving
> the problems I find with Dave Mills.
>
> >And why has the manual page never been updated, it is clearly wrong
> >when it talks about the contents of driftfile! :-(
>
> I updated neither the manpage nor the code because of the above.
>
> >> Anyway, ntpd4 is in CURRENT...
> >
> >Well... that won't help the 20 or so boxes here doing this all the
> >time:
> >Jan 1 11:26:46 gndrsh xntpd[133]: time reset (step) -0.217546 s
> >Jan 1 11:32:06 gndrsh xntpd[133]: time reset (step) 0.207523 s
>
> (-0.217546 - 0.207523) / (14 + 5 * 60 + 6) = -.001328340
>
> Your clock is too sick, (or our calibration of it is hosed), no
> version of {X}NTP will touch a clock which is outside +/- 500ppm.
>
> Could you try to measure the 14.31818... MHz base frequency and
> the 32768 kHz wristwatch xtal as well (I know you're RadioActive,
> so I pressume you have a counter ?)
>
> If they're both OK, then we have a code problem...
You have a code problem ;-)
I can confirm this behavior; its been consistent with xntpd for a LONG time,
which is why I raised the issue (it FINALLY got to the top of my "annoyance"
list).
--
--
Karl Denninger ([EMAIL PROTECTED]) Web: http://childrens-justice.org
Isn't it time we started putting KIDS first? See the above URL for
a plan to do exactly that!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
