client/server memory used incorrect

Rio <[email protected]>
Newsgroups gmane.comp.gnome.apps.gkrellm
Message-ID <[email protected]>

I am having an issue with the scrolling memory information. The used data is 
totally incorrect. 

example:

machine1:

free reports :
free -m
             total       used       free     shared    buffers     cached
Mem:          7934       1566       6367          0        364        890
-/+ buffers/cache:        311       7622
Swap:         3906          0       3906


glrellm client reports:

total 7934
used 71
free  7863


machine2:

free reports:
free -m
             total       used       free     shared    buffers     cached
Mem:         11962      11170        791          0       1355       2169
-/+ buffers/cache:       7645       4316
Swap:         3812          2       3809


gkrellm client reports:

total 11962
used 5313
free 6647


as you can see both 'used' reports are not accurate.

also on my workstation, in addition to the 2 clients for remote, my 
workstation reports are off too

free -m
             total       used       free     shared    buffers     cached
Mem:          1011        985         25          0         52        265
-/+ buffers/cache:        668        342
Swap:         3906        398       3508

gkrellm:
total 1011
used 590
free 421


the swap report for all 3 is accurate.

for the scroll i am using

$t - $u used - $f free

gkrellm version is 2.2.10 for both server and client.

the workstation is not so far off i cannot live with it, but the
client reports are too far off to be usable at all.

any idea what is wrong?

the server hardware is 2x dual core opteron using tyan 2882-D motherboards
(tyan gx28 servers)

the client hardware is 2x pentium3 coppermine using tyan s2507t motherboard.



chuck
_______________________________________________
Gkrellm mailing list
[email protected]
http://lists.jutley.org/cgi-bin/mailman/listinfo/gkrellm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.