Hi, 2012/11/22 Dejan Muhamedagic <[email protected]>: > Hi Lars, > > On Wed, Nov 21, 2012 at 04:43:08PM +0100, Lars Marowsky-Bree wrote: >> 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. > > I don't really want that the script gets modified either. > The above instructions are for people developing a new RA.
I like this, too. I would be useful when you need to diagnose in the production environment if you can enable / disable it without any modifications to RAs. It might be also helpful if it has a kind of 'hook' functionality that allows you to execute an arbitrary script for collecting the runtime information such as CPU usage, memory status, I/O status or the list of running processes etc. for diagnosis. -- Keisuke MORI _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
