On Mon, Aug 11, 2008 at 12:08:29PM -0600, Brad Nicholes wrote: > Actually this issue really isn't that hard solve. The python > capability is all implemented in the C module mod_python. When > mod_python's init() function is called, it simply reads the python > module directory from it's configuration and then starts a readdir() > loop on that location. Anything that it finds in the python module > directory that has an extension of .py, mod_python loads and calls the > module's metric_init() function. > > This behavior could be changed by simply adding a "Disabled=yes" or > "Status=disabled" type of directive to the module{} section for the > python module in it's configuration. Since gmond has already read and > parsed the entire gmond.conf including all 'included' .conf's, whether > a python module is loaded or not should be a simple matter of looking > for the module{} section for a specific module and checking to see if > it is enabled or disabled. If mod_python finds a .py file for a > module but can not find a corresponding module{} section in the > configuration, the enabled status is assumed to be 'disabled' > automatically. Otherwise the enabled state is assumed to be 'enabled' > unless otherwise indicated. If a python module is determined to be > disabled, mod_python would not load it and obviously the python > module's metric_init() would never be called. > > Does that work?
This will be perfect actually :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers