On 3/2/13 8:22 AM, Lars Marowsky-Bree wrote:
Unless it annoys you, this is actually harmless.
Otherwise, params first is what I tend to use.
Regards,
Lars
We've seen instances where failure-timeout is set, but Pacemaker never
seems to clean up the failure. First thought was it didn't
On 2013-03-03T12:29:55, David Coulson da...@davidcoulson.net wrote:
We've seen instances where failure-timeout is set, but Pacemaker never seems
to clean up the failure. First thought was it didn't actually utilize the
meta failure-timeout parameter if it was in the wrong place. Probably need
On 3/3/13 1:00 PM, Lars Marowsky-Bree wrote:
My memory may be very faulty, but I thought this didn't lead to the
failure actually be cleaned up automatically, but merely ignored
post-timeout.
Perhaps 'clean up' is the wrong phrase. But I've absolutely seen it
remove the failure out of 'crm_mon
Hi,
If req_lib_tmr_timerreschedule-timer_attributes.type is
SA_TIME_ABSOLUTE, an absolute time value must be higher
than the current absolute time.According to the type, we
will compare the current time with an absolute time. If
the type is SA_TIME_ABSOLUTE, we will compare. Or else,
