On Tue, 6 Feb 2001, Nico van Eikema Hommes wrote:

> Only during heavy disk activity (moving /usr/pkgsrc to another disk, full
> compile of a kernel, etc.), I see lines like the following in the syslog:
>
>    Feb  1 15:43:15 macbsd ntpd[147]: time reset 0.239779 s
>    Feb  1 16:14:19 macbsd ntpd[147]: time reset 3.545726 s
>    Feb  1 16:33:51 macbsd ntpd[147]: time reset 3.434815 s
>    Feb  1 16:56:31 macbsd ntpd[147]: time reset -0.318382 s

As far as platforms that can run ntp go, that's actually pretty bad.
:-)

Even my little 486 at work never jumps a whole second unless it's been
disconnected from the network for weeks.

> My /etc/ntp.conf contains no local clock, only the server lines pointing
> to our university's time servers. /var/db/ntp.drift contains "196.323".
> This is with 1.5, Jan.5 snapshot, almost -current kernel.

I bet the average latency spent in disk interrupts makes up a large
part of that, and that your "true" drift is much smaller. Is this with
or without soft updates?


Frederick