hey guys- i wanted to comment on the who "srclib" library business. there are two separate issues that need to be addressed.
first. i feel it is critically important that gmond be statically linked against all support libraries. there are sysadmins our there managing 1000s of ganglia machines and having a single statically linked binary makes it easy for them. imagine needing to do a yum update on thousands of hosts in order to make sure all rpm dependencies are met on upgrade. ouch. imagine using an os without a package manager and managing library dependencies. ooouch. second. i don't really care one way or another how the source for the support libraries gets on the _compile_ host since we will statically link against those libraries anyway. having them in the "srclib" directory gives us more control and makes it easier for people to download and compile. although it also makes packaging and maintenance for us a lot harder. i think it's best we talk as a group about what to do with "srclib" for a while since it's a complex issue but it shouldn't keep us from testing and releasing 3.0.4 sometime this month. it's very likely "srclib" will be addressed in a soon to be released release. my talk at linuxworld went well. i got to spend a few days hanging out with tobi oetiker (rrdtool), ian berry (cacti), remo rickli (nedi), kees cook (sendpage). tobi and i have been talking about ways to help with performance of rrdtool and reduce disk io. i've also been meeting with groundwork open source and they are planning to build a test cluster compromised of a number of different hardware/software platforms. hope you guys are having a good weekend. -matt
