On Fri, Mar 27, 2009 at 15:18, Joe Bill <foxyc...@yahoo.com> wrote: > > --- On Tue, 3/24/09, foxyc...@yahoo.com <foxyc...@yahoo.com> wrote: > >> ... what command should I type to cause the cluster to >> perform a "monitor" operation at a specific check level on >> that resource, and return the appropriate OCF status of the >> operation, *without* the cluster reacting like triggering a >> failover ? >> >> I'd love to see something like: >> >> # crm_resource -m check_level resource_id >> . >> < everything 'echo'ed by the monitor operation > >> . >> Resource 'resource_id' is (running normally / in a failed >> or undeterminable state / cleanly stopped). >> # >> >> ... and $? holding the OCF_status of the monitor >> operation. >> > > Amazing what a few minutes of serious thumb-sucking can produce. > The GUI shows an operation can be programmed for a given resource, and that > the operation has several parameters, among them 'on fail' with 'ignore' as > possible value. or, make sure that the specific monitoring operation always > 'exit 0' and save the monitor's real status elsewhere. > > The only issue left now is that the monitoring jobs are invoked periodically > and I'd like to have these invkoed just once, on demand.
Well there is lrmadmin which can talk directly to the lrmd. But I still have serious doubts about your concept in general. _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
