On Tue, Apr 22, 2008 at 3:12 AM, Carlo Marcelo Arenas Belon <[EMAIL PROTECTED]> wrote: > On Mon, Apr 21, 2008 at 12:37:10PM -0400, Jesse Becker wrote: > > > > Simply creating a gmond.conf.sample file is probably enough. That > > tripped me up the first time I built Ganglia from scratch--I spent a > > while looking around for the "default" gmond.conf file, and didn't > > find one. > > > > Just dump it into the root of the source tree, perhaps? > > # gmond -t > gmond.conf.sample > > it is explained in the README in the "Configuration" section.
Oh, I know *how* to do it, and that it is documented (which is how I figured it out in the first place). My point is that this is somewhat unexpected behavior: most programs supply a basic, working default configuration. Given that gmond can, in theory, run without any changes to the .conf file, there's all the more reason to provide a default file. It isn't like running 'gmond -t' during 'make' is difficult. -- Jesse Becker GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2 ------------------------------------------------------------------------- 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-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-general
