On 2012-11-21T16:33:18, Dejan Muhamedagic <[email protected]> wrote:
> Hi,
>
> This is little something which could help while debugging
> resource agents. Setting the environment variable __OCF_TRACE_RA
> would cause the resource agent run to be traced (as in set -x).
> PS4 is set accordingly (that's a bash feature, don't know if
> other shells support it). ocf-tester got an option (-X) to turn
> the feature on. The agent itself can also turn on/off tracing
> via ocf_start_trace/ocf_stop_trace.
>
> Do you find anything amiss?
I *really* like this.
But I'd like a different way to turn it on - a standard one that is
available via the CIB configuration, without modifying the script.
What would you think of OCF_RESKEY_RA_TRACE ? Our include script could
enable that; it's unlikely that the problem occurs prior to that.
- never (default): Does nothing
- always: Always trace, write to $(which path?)/raname.rscid.$timestamp
- on-error: always trace, but delete on successful exit
hb_report/history explorer could gather this too.
(And yes I know this introduces a fake parameter that doesn't really
exist. But it'd be so helpful.)
Sorry. Maybe I'm getting carried away ;-)
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
