Re: [Pacemaker] About updated attribute value output in the DC node

Hi Andrew, I confirmed that a patch was applied. http://hg.clusterlabs.org/pacemaker/devel/rev/6de803ca1a8e Thanks! Regards, Yoshihiko SATO (2011/07/08 16:44), Yoshihiko SATO wrote: Hi Andres, Thank you for comment. (2011/07/08 14:00), Andrew Beekhof wrote: On Tue, Jul 5, 2011 at 5:32 PM,

Re: [Pacemaker] About updated attribute value output in the DC node

Hi Andres, Thank you for comment. (2011/07/08 14:00), Andrew Beekhof wrote: On Tue, Jul 5, 2011 at 5:32 PM, Yoshihiko SATO wrote: Hi Andrew, Thanks for your quick reply. I remade the patch by the means to add to existing logic. (attachment : update_log1.patch) If it is possible, i want to

Re: [Pacemaker] About updated attribute value output in the DC node

On Tue, Jul 5, 2011 at 5:32 PM, Yoshihiko SATO wrote: > Hi Andrew, > > Thanks for your quick reply. > > I remade the patch by the means to add to existing logic. > (attachment : update_log1.patch) > > If it is possible, i want to get also the attribute names of XML("name", > "value") for log analy

Re: [Pacemaker] About updated attribute value output in the DC node

Hi Andrew, Thanks for your quick reply. I remade the patch by the means to add to existing logic. (attachment : update_log1.patch) If it is possible, i want to get also the attribute names of XML("name", "value") for log analysis. So, update_log2.patch is better for me. I would like to hear yo

Re: [Pacemaker] About updated attribute value output in the DC node

On Tue, Jul 5, 2011 at 12:36 PM, Yoshihiko SATO wrote: > Hi Andrew, > > Thank you for advice. > >> >> In this case I'd just append " $name=$value" >> > Sorry, I don't understand.. > Your meaning is checking the attribute name and value that are null or not? I mean to the log message. If its TYPE(

Re: [Pacemaker] About updated attribute value output in the DC node

Hi Andrew, Thank you for advice. In this case I'd just append " $name=$value" Sorry, I don't understand.. Your meaning is checking the attribute name and value that are null or not? Regards, Yoshihiko SATO (2011/07/05 10:39), Andrew Beekhof wrote: On Mon, Jul 4, 2011 at 8:05 PM, Yoshihik

Re: [Pacemaker] About updated attribute value output in the DC node

On Mon, Jul 4, 2011 at 8:05 PM, Yoshihiko SATO wrote: > Hi Andrew, > > Thanks for your comment. > > Do you mean that the output logic is branched by some conditions? Right > If my understanding is correct, What conditions should we judge? > "tag"(TYPE(reason)), "abort_text" or otherwise? > >  -

Re: [Pacemaker] About updated attribute value output in the DC node

Hi Andrew, Thanks for your comment. Do you mean that the output logic is branched by some conditions? If my understanding is correct, What conditions should we judge? "tag"(TYPE(reason)), "abort_text" or otherwise? - TYPE(reason) == "nvpair" Is it all right judging as attribute update?

Re: [Pacemaker] About updated attribute value output in the DC node

2011/6/28 Yoshihiko SATO : > Hi, > > I am setting location to the resource by using pingRA. > >    location location-grpPostgreSQLDB grpPostgreSQLDB \ >            rule -inf: default_ping_set lt 100 \ > > I watch the log of the DC node for the system observation. > However, the updated attribute va

[Pacemaker] About updated attribute value output in the DC node

Hi, I am setting location to the resource by using pingRA. location location-grpPostgreSQLDB grpPostgreSQLDB \ rule -inf: default_ping_set lt 100 \ I watch the log of the DC node for the system observation. However, the updated attribute values are only one output at each node. S