On Fri, Apr 11, 2008 at 4:09 PM, Jesse Becker <[EMAIL PROTECTED]> wrote:
> If there is an existing /etc/gmond.conf, then create a new "patched" > file as something like /etc/gmond.conf.upgrade_from_3.0.x. This > leaves the existing file alone, reducing the risk of breaking > something. Also, a big message about moving this file into place > should also be displayed, telling the admin that to finish the > upgrade, they need to move the new file into place. Actually if /etc/gmond.conf exists, the current spec file would automatically moved to the new location /etc/ganglia/. BTW, the proposed solution wouldn't work, because %preun which is executed is of the previous version (i.e. 3.0.x) and thus it wouldn't be possible to get a vanilla copy of the previous version's gmond.conf. So if we want this automated, perhaps we need to put the diff in the code some where... gmond does have an argument --convert for converting from 2.5.x to 3.0.x, maybe we can extend it... but not too sure at this point. Cheers, Bernard ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
