>>> On 2/1/2011 at 12:02 PM, in message <aanlktikuk0fsydcm04tzz6kg6mdy6u8borhhcuinv...@mail.gmail.com>, Bernard Li <bern...@vanhpc.org> wrote: > Hi all: > > When I was writing a Python module for monitoring GPU metrics, I > noticed that the interface does not provide a way to set dmax. > According to the gmetric man page, dmax is: > > -d, --dmax=INT > The lifetime in seconds of this metric (default=*0*) > > So I was wondering why this isn't available for the Python or C module > interfaces. > > Right now, if I had added a new metric via the interfaces and no > longer want it, I would have to: > > 1) Comment it out in the conf > 2) Restart the gmond where the module originates from > 3) Restart the collector gmond > 4) Restart gmetad >
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. Brad ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
