On Mon, Jul 13, 2009 at 04:49:17PM +0100, Daniel Pocock wrote:
Brad Nicholes wrote:
On 7/13/2009 at 8:17 AM, in message
e6ccb7f50907130717i2f3dfd5fi1c69dbd4124a7...@mail.gmail.com, utopia zh
utopia...@gmail.com wrote:
Hi,
While trying to use gmond to monitor our
Hello,
I apologize to bother you all with this issue, but it seems to have
stumped those in the ganglia-general mailing list, so I'm hoping the
developers could help me out.
I'm using Ganglia v3.0.3 on openSUSE 10.3 which came pre-configured on a
Microway cluster. It's slightly modified to
One way to make it non-disruptive for 3.1 would be making this new
behavior configurable (as I suggested in the bug) - is it worth the
extra effort of adding a config option for this, or is 3.2 intended to
be released in the new future?
There isn't a planned date for a 3.2
I can use gmetric to feed the information to gmond and have it show the
correct uptime:
snip
./gmetric --name=boottime --value=`grep btime /proc/stat | awk '{ print
$2 }'` --type=uint8
snip
However, when I do this, boottime disappears, but uptime is correct so
long as I do not restart gmond.
