Verner Kjærsgaard wrote: > Hi list, > > - I've read and searched and read and searched all vmware docs and more...and > still, I take the liberty to ask this list. Its got a little to do with > SuSE10.2, so please forgive me... > > - I'm running SLES10 as a host OS onto which I'm running a number of > SuSE10.2s > using vmware server. My time in the quests is way off. I set it using > ntpdate -s on the clients. Then I initiate ntpd on the client. Or not, no > difference. The time in my clients lacks behing by several hours/day. > > - I'm currently trying a real dirty hack...on the client I'm running a > cronjob > every 10 minutes, doing a ntpdate -s -b IP-OF-TIMESERVER. I tried that hack > by running the cronjob every 30 minutes, - but that didn't work...
Sadly, vmware is broken in this regard. We found that vmware guests simply have no way to keep accurate time. We've resorted to running ntpdate in a cron job every minute, which still gives us 15 second jumps. Most serious applications can't tolerate that sort of time inaccuracy. Joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
