I think this mostly works out:
* https://github.com/ganglia/monitor-core/pull/183
* https://github.com/ganglia/gmond_python_modules/pull/184
On 02/06/2015 09:35 AM, Chris Burroughs wrote:
That makes sense. For me in the import short term the thing is not
manually trying to keep dupe code
You could change the location of all modules with modpython.conf, but
I'm not sure there is a way to add multiple locations to the search path.
What is the problem you are running into with one directory? I've
usually had success with having $INSERT_CONFIG_MNGMT_TOOL drop in
additional files.
Thanks Chris for doing this.
Vladimir
On 02/09/2015 10:05 AM, Chris Burroughs wrote:
I think this mostly works out:
* https://github.com/ganglia/monitor-core/pull/183
* https://github.com/ganglia/gmond_python_modules/pull/184
On 02/06/2015 09:35 AM, Chris Burroughs wrote:
That makes
That makes sense. For me in the import short term the thing is not
manually trying to keep dupe code in sync. I'll start work on reconciling.
On 02/05/2015 02:45 PM, Dave Rawks wrote:
IIRC at least some of the motivation behind the current split had to do
with separating out modules which
Is there best practices for separating custom/contrib gmond python
modules from the packaged ones ?
Currently I have to install everything under lib64 (ie.
/usr/lib64/libganglia/python_modules) on our redhat boxes. It would be
easier to do sysadmin tasks if the custom ones had a different
IIRC at least some of the motivation behind the current split had to do
with separating out modules which aren't generally platform agnostic
since platform specific stuff sometimes causes problems with downstream
linux distro adoption/packaging. I.E. the official python modules
should be
