[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gomd-devel] Re: <GOMD> GOMDVIEW & DAEMON updated
From: |
Gian Paolo Ghilardi |
Subject: |
[gomd-devel] Re: <GOMD> GOMDVIEW & DAEMON updated |
Date: |
Sat, 10 Apr 2004 22:27:22 +0200 |
Hi Matt.
>
> btw1 : i re-checked + tested the latest changes on gomdview
> and it works nice for me too.
Me too :)
>
> btw2 : updated gomdview.cpp in the cvs and changed the
> open_remotecon method to use the lg object.
> Could you please re-check ? it is not yet working for me ;))
> (take your time, will look into it a bit more the next days if time)
open_remotecon() or the whole program doesn't work? Here all works fine. :)
Did you start the autodiscovery for the daemon so it can fill the
/etc/knownGomds cache file? ("start ad 10" => will search the daemon on
local node from X.Y.Z.1 to X.Y.Z.10).
My idea about using the libgomd class (feel free to drop it if not needed
:) )
string lall;
string mall;
Vector loadValues;
Vector memValues;
THREAD LOOP
if(lg.openConn(...)==true)
{
lall = lg.getInfo("get load ALL");
mall = lg.getInfo("get mem ALL");
...
lg.closeConn();
...
loadValues parseValue(lall); //fill a vector with found load values
memValues parseValue(mall); //fill a vector with found mem values
setLoadGauges(loadValues); //set QT-based gauges for load values
setMemGauges(memValues); //set QT-based gauges for mem values
...
}
...
CLOSE LOOP
Bye.
<JP>