On Sun, Dec 06, 2009 at 05:09:08PM +0000, Paul Sobey wrote: > On Saturday 05 December 2009 18:01:00 Carlo Marcelo Arenas Belon wrote: > > > > (*) this is not the official 3.1.5.2139 package but one that was patched > > additionally with relevant backports from trunk and bootstrapped in > > Centos 4 for added injury. > > Compiles perfectly against a new python 2.6.2 - thankyou! I thought the > following thread might be of use: > > http://bugs.python.org/issue1759169 > > but it would seem that I was either wrong or that you've worked around it.
that it is still relevant for your python binaries as you would have otherwise problems if using C99. the ganglia package you used worked around it by not building with C99 (which is what bootstrapping with CentOS 4 does) but still getting a fix for BUG215 so it wouldn't need to tweak CC or CFLAGS : http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=215 > I haven't tested it yet - will do so tomorrow. It should work fine but if you are feeling brave and want to try what would happen also if using C99 then try (beware the name of the package was changed but will still unpack over the same directory, so you need to cleanup after building one package if looking at the other): http://sajino.sajinet.com.pe/ganglia/el4-ganglia-3.1.5.2145.tar.gz (!C99) http://sajino.sajinet.com.pe/ganglia/f12-ganglia-3.1.5.2145.tar.gz (C99) the package that was bootstrapped in fedora 12 (f12) would use C99 to build the ganglia sources while the other package (el4) should be otherwise equivalent to the one you tested before. > I was under the impression that > the python module was needed to get per volume disk stats, is that not the > case? there is a python module called multidisk.py that does that, but AFAIK it doesn't support ZFS and is linux (might work partially in others) only though. > We have lots of zfs volumes and I'd like to be able to graph usage of > each, and hopefully use rrd's trending to get some sort of prediction when > I'll need a bigger fileserver. fixing multidisk.py to understand zfs (specially the difference between zpools and file systems) would be a solution for that and unless you decide to ignore the extra metrics which will be created otherwise, most likely (if it even works) you can also make a script which will collect the values you will be interested and use gmetric to generate the right metrics as an alternative (which doesn't require python support and would work even with ganglia 3.0) > Also is it safe to use this version with a > collector gmond @3.1.2 or should I upgrade all? That's a slightly more > tiresome operation which take me a while a longer... all version of 3.1.x are compatible between them, so you don't really need to upgrade all the others, unless you want to. Carlo ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Ganglia-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
