On Wed, Jun 02, 2010 at 12:08:51PM +0200, Lars Marowsky-Bree wrote: > On 2010-06-01T00:37:24, Lars Ellenberg <[email protected]> wrote: > > > Once we notice, what are we supposed to do? > > Not do any action ourselve, > > but tell pacemaker the resource has failed, > > because that is where $policy lives? > > Yes, that's it, I think. > > Sorry for the outburst, I'm really overly ripe for a vacation. > > > $your_non_backgrounding_process_here > > # unless you decide based on "something" > > # that this was an expected exit: > > crm_resource -F > > > > still too simple? > > No, this would be ok, but I'd still like to see it integrated with lrmd.
... > At the end, we'd have almost the complexity needed to make lrmd proper > handle it, but with more load overhead on the system. > > So I appreciate the simplicity of implementing it in shell, but still > deem lrmd to be the better place. ... I'd not put it into the RA. I'd write a wrapper around whatever process is supposed to run. maybe a shell script, or a shell function. somthing like that: call_crm_resource-F_on_process_exit.sh #!/bin/sh # takes OCF_RESOURCE_INSTANCE from environment, # would need to check that that exists "$@" crm_resource -F -r $OCF_RESOURCE_INSTANCE and, for example in the "anything" RA, instead of "this-and-that args", you use call_crm_resource-F_on_process_exit this-and-that args -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
