What hardware are you running on the host? Intel? AMD?
Take a look at
http://www.vmware.com/community/message.jspa?messageID=475075 for a
decent discussion of timekeeping in vmware. I remember coming across
articles saying it's much less effective to run ntpd and ntpdate in
vmware guests -- the skew can still be hours until the next update.
That prompted us to switch from vmware to xen on one of our virtual hosts...
Do you have vmware-tools installed? Have you tried 'clock=pmtmr' or
'clock=pit' at boot?
Does your vmx file specify tools.syncTime = "TRUE"?
Basura basura02-at-contuvieja.com.ar |qmailtoaster/1.0-Allow| wrote:
is ntp deamon installed with the iso dist by default?
if so, how can i tell the deamon to doit every minute?
thanks, I´m really desperate with the vmware server clock issue.
slamp slamp escribió:
well if you are concerned about time and want to update it every
minute why not just run the ntp daemon? thats how i have mine setup.
On 8/26/07, Basura <[EMAIL PROTECTED]> wrote:
you are right. * * * * * is every minute. In fact, if I change the
command to "echo x >> /txt" it writes a new line every minute at /txt,
but the "/usr/sbin/ntpdate time.nist.gov > /dev/null 2>&1 " dose not work.
FK
Jean-Paul van de Plasse escribió:
Just curious why is it set to never run?
* * * * * would normally be every minute..
JP
----- Original Message ----- From: "Jake Vickers" <[EMAIL PROTECTED]>
To: <qmailtoaster-list@qmailtoaster.com>
Sent: Sunday, August 26, 2007 9:44 AM
Subject: Re: [qmailtoaster] cron not working as expected
Basura wrote:
Hi all,
My qmail is the latest qmailtoaster plus ISO.
I need to run the following cron as root
* * * * * /usr/sbin/ntpdate time.nist.gov > /dev/null 2>&1
"/usr/sbin/ntpdate time.nist.gov" is executed perfectly at the
console, but as a cronjob using crontab it doesn´t work.
It's set to never run. It needs to be something like:
35 * * * * /usr/sbin/ntpdate time.nist.gov
What I do on my machines is create a script:
#!/usr/sh
# updatetime script
/usr/sbin/ntpdate time.nist.gov
And drop it into my /etc/cron.hourly folder and make it executbale
(chmod +x /etc/cron.hourly/updatetime).
You shouldn't need to update the time more than once an hour. If it's
getting more than a couple thousandths of a second off in an hour you
either have a motherboard issue or one that has a REALLY cheap clock.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
