<br><br><div class="gmail_quote">On Wed, Dec 23, 2009 at 8:34 AM, Dejan Muhamedagic <span dir="ltr"><<a href="mailto:dejanmm@fastmail.fm">dejanmm@fastmail.fm</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
> > > 3. Why the pingd attribute was not set immediately after pingd started<br>
> > > up, and was able to ping the ping node. After the pingd was started, then<br>
> > > it waited 60 seconds (the timeout value) to set the attribute so that<br>
> > > then the XEN resources were able to start, due to their location<br>
> > > constraint.<br>
> I must have observed this somehow falsely. The pingd attribute was set only<br>
> some seconds after the pingd was started on the nodes. However, the depending<br>
> XEN resources, were only started about a minute after that happend.<br>
> Is there any parameter I can use to shorten that time frame from a minute to<br>
> some seconds?<br>
<br>
</div>Don't think so. I don't understand why it waited.<br></blockquote><div><br>The pingd resource has "dampen" instance parameter. The pingd udpate is delayed by dampen time. The default value is 1 sec. Unless you set it to 60s, it should update every 1 sec. I think something is wrong in your case. The pingd is working fine in my system.<br>
<br>Thanks<br>hj<br></div></div><br>