on 5-21-2008 2:39 PM Bjørn T Johansen spake the following:
Why not? I have been running ntp inside vmware for many years now, without any
problems
And I occasionally fail to come to a full stop at a stop sign, and don't get a
ticket, but is it the proper thing to do?
--
MailScanner is
the short explanation is that both the VM container and ntp adjust the
clock tick, and both think they are the only application that does so.
There are longer explanations in many places around the internet.
On 2008 May 21 (Wed) at 23:39:17 +0200 (+0200), Bj??rn T Johansen wrote:
:Why not? I h
Why not? I have been running ntp inside vmware for many years now, without any
problems
BTJ
On Wed, 21 May 2008 12:30:01 -0700
Peter Hessler <[EMAIL PROTECTED]> wrote:
> never ever ever run ntp on virtual hardware.
>
> instead, run ntp on the host hardware, and tell the client to always
>
Thank you for the prompt answers
@Luuk Vosslamber
>finding correct values for the following entrys in your vmware(host)
>config file might solve some things:
>host.cpukHz = 1596000 <== depends on processor speed ;-)
>host.noTSC = TRUE
>ptsc.noTSC = TRUE
>hostinfo.noTSC = TRUE
>tools.syntime =
never ever ever run ntp on virtual hardware.
instead, run ntp on the host hardware, and tell the client to always
obey the bios clock. I add "* * * * * /sbin/hwclock --localtime --hctosys"
to my crontab for that.
On 2008 May 21 (Wed) at 20:27:09 +0200 (+0200), Robert Henjes wrote:
:
:Hi,
:
:I
At 8:27 PM +0200 5/21/08, Robert Henjes wrote:
Hi,
I followed the discussions regarding the "time moved backward" problem
and the use of ntp in such cases. At our department we are running two
dovecot servers within an vmware server environment, and unfortunately
the timedrift (with ntpd active)
