Description of problem: A tool for diagnosing magma's environment would be very beneficial when troubleshooting. One particular use case that we encountered today was that magma was looking in /usr/src/build/507093-x86_64/install/usr/lib64/magma for the plugins instead of /usr/lib64/magma. This was a bug in the build system, but it was difficult to debug without running strace on a program that used magma (I used `strace /sbin/cpt lock`). A diagnostic tool that reported where it was looking for the plugins would have saved some time. Additionaly, this tool could also be used to test the magma interfaces much like cpt does today. Infact, cpt would be adequate resolution to this bug if it also was capable of providing more feedback as to the state/configuration of the system (e.g. where the plugins directory is). If cpt is used, perhaps a more appropriate name should be used that is consistent with the rest of the Cluster Suite program names (e.g. magma_tool) There should also be appropriate man pages describing this tool: Version-Release number of selected component (if applicable): Not available in magma-1.0-0.pre17.0.x86_64.rpm or earlier Expected results: Perhaps the output of the tool might look something like this: # magma_tool plugins Magma version: 1.2.3 plugins directory: /lib/magma magma-plugins: magma_gulm.so magma_sm.so magma_xxx.so # magma_tool test Connected via: GuLM Plugin v1.0
Adding a plugin list would require adding APIs to magma. These APIs would not be of the mainline magma-stuff. Instead, they'd simply be debugging functions which would be called by cpt (which would now be called magma_tool).
Added magma_tool and magma_tool manpage with all the aforementioned features, including ability to enable/disable plugins from the command line. (just does chmod, really).