Today, Jason A. Smith wrote forth saying...

> I would actually suggest keeping a default gmetad.conf file in the
> package as an example, even if it is just all the default parameters
> commented out.  Does the package come with a default gmond.conf package
> as well, I don't see it in the file list.

/etc/gmond.conf and /etc/gmetad.conf will both be added to the package 
with all the options commented out.

> I would also suggest splitting the package into gmond and gmetad
> sub-packages since gmetad isn't needed on all of the monitored nodes.

we may do that in the future if gmetad grows into a crazy beast of a
daemon (which i don't see happening but...).  for now, it's only a single
500k binary (linux ELF).  which i don't think necessitates a separate
package just yet.  of course, it will not be setup to run by default, but
will be there to easily activate if you want a host to start collecting
and saving data (using chkconfig).

-matt



> 
> On Thu, 2002-09-19 at 15:00, Federico David Sacerdoti wrote:
> > 
> > I'm going to change a few things with the ganglia-monitor-core RPM spec 
> > file 
> > and packaging.
> > 
> > 1. There is no /var/lib/ganglia folder created.
> > 2. The /etc/gmetad.conf file does not get installed.
> > 3. Documentation? 
> > 
> > Matt, the other thing is this: Is there a way to specify gmetad polling 
> > intervals on a per-datasource basis? That would be very useful, especially 
> > when some sources are close, and some are far away over potentially slow 
> > links. Maybe something to put into a 2.5.1 release.
> > 
> > Federico
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Ganglia-developers mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/ganglia-developers
> 



Reply via email to