<div><font color="#660066">2011/7/22 Dan Urist wrote: <br>> I am in the process of trying to write an fping RA, based on the <br>> pacemaker ping RA. My impetus for this is that I would like the RA to <br>> return success as soon as any ping succeeds; the behavior of linux's <br>
> system ping as used in the standard ping RA is to run COUNT pings <br>> within the given deadline and only after COUNT or the deadline return <br>> success if any of the pings succeeded-- very inefficient. <br>
> <br>> My question is this: the ping RA sets default values for <br>> OCF_RESKEY_CRM_meta_timeout and OCF_RESKEY_CRM_meta_interval, and it <br>> tests that OCF_RESKEY_CRM_meta_interval is an integer greater than 0. <br>
> These variables aren't used anywhere else within the RA, but these are <br>> the same values in the "actions" section of the metadata for the monitor <br>> timeout and interval. I can't find any documentation that these <br>
> variables serve as defaults for the monitor action in either the OCF <br>> agent developer guide or the pacemaker docs, but this seems to be the <br>> intent. Is this what they're there for? <br></font></div>
<div> </div>
<div> I think so.</div>
<div>The values in the "actions" section of the metadata for the monitor timeout and interval, are used as monitor operation's default values.</div>
<div>OCF_RESKEY_CRM_meta_timeout and OCF_RESKEY_CRM_meta_interval are come from the monitor operation's actual values.</div>
<div> </div>
<div> </div>
<div> </div>
<div>Best Regards, <br>Yingliang Yang<br> <br>_______________________________________________<br>Pacemaker mailing list<br><a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br><a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a></div>