On Sat, Aug 05, 2006 at 11:37:26PM +0200, Thomas Schwinge wrote:
> Aug 5 21:29:46 taylor ntpd[4318]: adjusting local clock by -2.431421s
send(3, "<30>Aug 5 21:29:46 ntpd[4318]: "..., 67, MSG_NOSIGNAL) = 67
adjtimex({modes=32769, offset=-2230536, freq=0, maxerror=16384000,
esterror=16384000, status=64, constant=2, precision=1, tolerance=33554432,
time={1154806186,
324677}}) = 5
> Aug 5 21:34:07 taylor ntpd[4318]: adjusting local clock by -2.529765s
send(3, "<30>Aug 5 21:34:07 ntpd[4318]: "..., 67, MSG_NOSIGNAL) = 67
adjtimex({modes=32769, offset=-2300611, freq=0, maxerror=16384000,
esterror=16384000, status=64, constant=2, precision=1, tolerance=33554432,
time={1154806447,
833571}}) = 5
> Aug 5 21:36:54 taylor ntpd[4318]: adjusting local clock by -2.584983s
send(3, "<30>Aug 5 21:36:54 ntpd[4318]: "..., 67, MSG_NOSIGNAL) = 67
adjtimex({modes=32769, offset=-2446443, freq=0, maxerror=16384000,
esterror=16384000, status=64, constant=2, precision=1, tolerance=33554432,
time={1154806614,
408484}}) = 5
> Aug 5 23:09:04 taylor ntpd[4318]: adjusting local clock by -4.626432s
send(3, "<30>Aug 5 23:09:04 ntpd[4318]: "..., 67, MSG_NOSIGNAL) = 67
adjtimex({modes=32769, offset=-4468765, freq=0, maxerror=16384000,
esterror=16384000, status=64, constant=2, precision=1, tolerance=33554432,
time={1154812144,
410368}}) = 5
So, atleast, the kernel seems to know about some offset now.
If I just look at how fast the clock changes, it seems you're drift
about 1 second every hour, which seems to be to be rather large value.
If my memory is correct, the kernel has a limit of
adjusting 500 ppm, so that would be 1.8 seconds / hour.
So either you're clock is drifting faster than that, or
the kernel isn't doing the right thing.
Maybe you should try playing with the adjtimex util, and
set the tick (or freq) value, so that it should keep time
better. I wish openntpd would do this by itself, but it
doesn't.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
