This is caused by the clock running too high on default Debian (probably
all Linux) kernels. Some later kernels have this option in .config in your
kernel source tree, and buried somewhere in the make menuconfig (or however
you are making your config). Look for an option called "CONFIG_HZ", by
default (in old kernels, where it was not configable) it was 1000 HZ as
defined in I think parm.h somewhere?). With newer kernels (above around
2.6.8) its now in .config with a default value of 250, change it to 100,
and recompile.
Verify workingness by running ntpdate manually every few minutes, or after
an hour to make sure time hasnt messed up by more then a second per
hour. DON'T use ntpdate to fix this problem (as in using in cron every few
minutes). once an hour at most.
Combined with the CONFIG_HZ=100, you can try the various clock=pit, noacpi,
etc.. etc.. but those typically didn't work for me back when we researched
the problem.
Also, be sure to install VMWare Tools in your VM, and set it up to sync the
clock with the host.
We happen to be running Debian here as both VMs and normal machines. On my
desktop, Intermapper remote runs nicely on a Debian box with 4 displays.
- - - Jon Myers
Network Manager
Alfred State College
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
