John Hasler wrote:
> Frank writes:
>> My ntp client changes clock (by small amount) at any time:
>> Jul 25 05:29:38 bax ntpd[10269]: adjusting local clock by 0.098724s
>> Jul 25 05:31:43 bax ntpd[10269]: adjusting local clock by 0.038991s
>> Jul 25 06:13:38 bax ntpd[10269]: adjusting local clock by -0.037131s
>> Jul 25 15:01:52 bax ntpd[10269]: adjusting local clock by -0.112429s
>
> Ken writes:
>> These do seem to be larger values than you might expect from a clock
>> conditioned with ntpd. Is it a VM or is there something going on that
>> would stop or suspend your system?
>
John writes:
> There is certainly something wrong there.
I saw very bad clock performance on one Linux box I had (dual-single core
AMD cpus, no VMs), even with NTP, until I changed the clocksource kernel
parameter to hpet. Unfortunately (or fortunately) I no longer have that box.
--
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.