i just uploaded a new snapshot of 2.6.0. to http://matt-massie.com/ganglia/ganglia-2.6.0.200412131710.tar.gz
the main changes are in the ./lib/protocol.x definition and ./gmond/gmond.cif you run gmond now, it will output messages to stderr about the messages it hears. it looks something like...
% ./gmond -d10 -c ./gmond.conf 169.229.48.130 =>bytes_in 169.229.48.92 =>pkts_in 169.229.48.111 =>bytes_in 169.229.48.111 =>pkts_in 169.229.48.99 =>bytes_out 169.229.48.115 =>heartbeat 169.229.48.115 =>pkts_out 169.229.48.83 =>heartbeat 169.229.48.74 =>bytes_out 169.229.48.58 =>bytes_in 169.229.48.109 =>load_one 169.229.48.145 =>cpu_system 169.229.48.79 =>mem_sharedthis 2.6.0. gmond is capable of understanding xdr from 2.5.x sources but there is a catch: only linux and freebsd are completely supported.
reading over the old metric array i realized that the freebsd guy (brooks?) did the right thing. the freebsd metric list matches the linux list exactly. nice.
for solaris, HPUX, Tru64, et al. the first 29 metrics will work (which covers a good number of them) but gmond will ignore the rest.
this gmond will even understand gmetric messages sent from 2.5.x clients.if you want to learn about how processing xdr data works... everything is defined in ./lib/protocol.x especially the function at the bottom ganngliaOldMetric_get() which has the static metric array information.
to be clear, i'm not saying that 2.6.0 on non-linux/freebsd boxes will lose any metric support (if all gmond are 2.6.0)... it's only the backward compatibility that is limited. my hope is that the new xdr format will allow us to modularize and grow the metric set rapidly and easily.
-matt
--
PGP fingerprint 'A7C2 3C2F 8445 AD3C 135E F40B 242A 5984 ACBC 91D3'
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
--Benjamin Franklin, Historical Review of Pennsylvania, 1759
signature.asc
Description: OpenPGP digital signature
