On Mon, Jan 31, 2005 at 05:13:23PM +0000, Matt Massie wrote: > i've just built what i think it a complete snapshot (meaning all > features are working as they should). > > this latest snapshot adds > - support for "ttl" on multicast udp_send_channel definitions > - fixed a minor bug in cygwin metric collection > - has brooks fix for preventing a memory leak on freebsd in low memory > conditions > > i've built all the file formats for a release at > http://matt-massie.com/ganglia/2.6.0/ > > if you want an old snapshot for some reason, they are available at > http://matt-massie.com/ganglia/2.6.0.archive/ > > the rpms seem to work (i installed gmond/gmetad/web and it worked). > > i have a question about the rpms. > > i don't know exactly how to handle the configuration file conversion. > currently, the rpm installs and default gmond.conf in /etc/ unless a > file by that name exists and then it creates the file as > /etc/gmond.conf.rpmnew. > > to convert the file requires something like > > % mv /etc/gmond.conf /etc/gmond.conf.bak > % gmond --convert /etc/gmond.conf.bak > /etc/gmond.conf > > i don't know if i really want that in the rpm (other than echoing the > need to run the commands to the terminal). > > to do this Right i'll need to build code to determine if a configuration > file is version 2.5.x or 2.6.x (which i don't have yet). the logic > would be something like. > > if(/etc/gmond.conf doesn't exist) > install the rpm default /etc/gmond.conf > if(/etc/gmond.conf DOES exist) > { > if(/etc/gmond.conf is old format) > convert to new format > else > install new rpm gmond.conf as /etc/gmond.conf.rpmnew > } > > i always get nervous making too many things automatic (it seems it > always bites you) especially given the trusted_hosts option might get > mangled or something (it shouldn't but things happen). > > how would you guys like the rpm to behave? what makes sense?
I agree that automatic upgrades are likely to bit us some place painful. For the FreeBSD port, I'll be putting an entry in the UPDATING file that lists ports which have incompatable changes. I think there's a strong argument that this should be 3.0 not 2.6.0. A complete rewrite of the config file format seems worth a major version bump (it's not like they cost much :-). The fact that the under-pinnings have changed to apr also leads me in this direction. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
pgpc7QI8U66Va.pgp
Description: PGP signature
