Hey,

I have tried out 3.0.0 on windows. I had to edit the confuse/tests makefile to get it to compile. The default gmond.conf has setuid = yes, which causes gmond to fail on start. The installer works nice too.

I played around with sending unicast UDP to another gmond (that was on multicast as well), and when it was set to receive on that unicast channel it saw the unicast gmond, but it didn't tell anyone else in the multicast channel about that host. I assume this is because all that it sends on the multicast channel is updates about itself.

So now the weird part. If the unicast gmond doesn't have itself listening to itself, it doesn't know about itself. So if I have the following:

udp_send_channel {
 host = 127.0.0.1
 port = 8679
}

/*udp_recv_channel {
 port = 8679
}*/

(or vice versa) and I query the tcp port, ganglia knows nothing interesting. This is what you would expect. But it blows my mind that a unicast gmond doesn't share data about itself, with itself, unless explicitly stated. I think this is the correct behavior, but it is hard to understand at first.

Ian

Matt Massie wrote:

i'm assuming no news is good news. are you guys having any problems with 3.0.0? i've run tests on solaris, freebsd, linux ia64 amd64, windows, macos x and it seems like it compiles and runs well.

are the rpms working out for you?
http://matt-massie.com/ganglia/

does the announcement look good (meaning.. are you sure i haven't forget to mention any cool stuff you did to make this release a reality).
http://matt-massie.com/ganglia/WHATS_NEW.txt

-matt



Reply via email to