Hi,
On Tue, 2009-01-27 at 14:19 +0100, Dejan Muhamedagic wrote:
> Hi,
>
> On Fri, Jan 23, 2009 at 11:53:58PM +0800, Yan Gao wrote:
> > Hi,
> > On Fri, 2009-01-23 at 16:37 +0100, Dejan Muhamedagic wrote:
> > > Hi,
> > >
> > > On Fri, Jan 23, 2009 at 10:59:56PM +0800, Yan Gao wrote:
> > > > On Fri, 2009-01-23 at 15:05 +0100, Michael Schwartzkopff wrote:
> > > > > Hi,
> > > > >
> > > > > I got the lates verison of the pacemaker GUI running on my test
> > > > > system. Now a
> > > > > output of the management window gives you much more info about
> > > > > specific
> > > > > resources. I.e. it displays info about operations taken on a specific
> > > > > resource.
> > > > >
> > > > > Greate feature! Thanks.
> > > > :-)
> > > >
> > > > >
> > > > > Now my question:
> > > > > I see the monitoring operation in that window and the "Last Run" time
> > > > > does NOT
> > > > > change in normal operation, although the resoruce is beeing monitored
> > > > > in the
> > > > > background. Only when I disturb the resource (i.e. kill apache
> > > > > manually) and
> > > > > pacemakder restarts it, I can see the time changes.
> > > > Yes, the information won't be refreshed until the result of an operation
> > > > changes (such as monitor) or there's a new operation called (such as
> > > > start, stop)
> > > > If you want to see the real updated info, you have to click the
> > > > "Refresh" button to refresh the cib from lrm
> > > > >
> > > > > What is then the meaning of the "Last Result Change" colunm, which in
> > > > > fact
> > > > > displays always the same info?
> > > >
> > > > It indicates when the last time that the return code of an operation
> > > > changed was.
> > >
> > > Should have probably been named "Last Status Change" time.
> > > Probably my bad.
> > There's another attribute of "lrm_rsc_op" that is named
> > "op-status" ("Status" field in GUI) used for indicating whether an
> > operation is "complete" or "pending".
> > That's somewhat confusing:-)
>
> Agreed...
>
> > Any other suggestion?
>
> ...but I have no idea how else to name it. Actually, I think that
> op_status is fine here. The other "status" should probably be
> called op_outcome or something like that. Then, we could have
> rsc_status which would be "running", "stopped" and such.
Or for now we could just call them "Return Code" and "Last Return Code
Change" for avoiding confusion:-)
--
Regards,
Yan Gao
China R&D Software Engineer
[email protected]
Novell, Inc.
Making IT Work As One?6?4
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
