Hi Brad: On Tue, Feb 1, 2011 at 4:51 PM, Brad Nicholes <bnicho...@novell.com> wrote:
> I would probably have to go back and figure out what I was thinking at the > time, but I vaguely recall that dmax was hardcoded for all of the standard > metric in the 3.0 version of gmond. So at the time I was probably thinking > that exposing dmax just wasn't necessary. That was probably a wrong > assumption. Thinking back now, it would have made since for dmax to be > hardcoded in 3.0 because there was no way to add or remove metrics in that > version. But in the 3.1 version where you can do it, dmax shouldn't have > been hardcoded and should have been exposed. With gmond 3.0, you should be able to add metrics using gmetric. Anyway, I've just filed a feature request to better keep track of this issue: http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=297 Thanks, Bernard ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
