$NetBSD: patch-al,v 1.1 2005/02/10 02:33:53 jschauma Exp $ --- ganglia.html.orig 2005-02-07 22:25:39.000000000 -0500 +++ ganglia.html 2005-02-07 22:26:58.000000000 -0500 @@ -278,7 +278,7 @@ example, you may not want to have gexec run jobs on your cluster frontend nodes.

You simply add the following line to your gmond configuration file (/etc/gmond.conf by +

You simply add the following line to your gmond configuration file (@PKG_SYSCONFDIR@/gmond.conf by default)

@@ -383,16 +383,16 @@

The configuration file format has changed between gmond version 2.5.x and version 2.6.x. The change was necessary in order to allow more complex configuration options.

Gmond has a default configuration it will use if it does not find the default configuration -file /etc/gmond.conf. To see the default configuration simply run the command:

+file @PKG_SYSCONFDIR@/gmond.conf. To see the default configuration simply run the command:

   % gmond --default_config

and gmond will output its default configuration to stdout. This default configuration can serve as a good starting place for building a more custom configuration.

   % gmond --default_config > gmond.conf

would create a file gmond.conf which you can then edit to taste and copy to /etc/gmond.conf +

would create a file gmond.conf which you can then edit to taste and copy to @PKG_SYSCONFDIR@/gmond.conf or elsewhere.

To start gmond with a configuration file other then /etc/gmond.conf, simply specify the +

To start gmond with a configuration file other then @PKG_SYSCONFDIR@/gmond.conf, simply specify the configuration file location by running

   % gmond --config /my/ganglia/configs/custom.conf

@@ -411,7 +411,7 @@

Gmetad Configuration

The behavior of the Ganglia Meta Daemon is completely controlled by a single configuration -file which is by default /etc/gmetad.conf. For gmetad to do anything useful you much +file which is by default @PKG_SYSCONFDIR@/gmetad.conf. For gmetad to do anything useful you much specify at least one data_source in the configuration. The format of the data_source line is as follows

@@ -574,7 +574,7 @@
     -h, --help          Print help and exit
     -V, --version       Print version and exit
     -c, --conf=STRING   The configuration file to use for finding send channels
-                        (default=`/etc/gmond.conf')
+                        (default=`@PKG_SYSCONFDIR@/gmond.conf')
     -n, --name=STRING   Name of the metric
     -v, --value=STRING  Value of the metric
     -t, --type=STRING   Either
@@ -586,7 +586,7 @@
                         (default=`60')
     -d, --dmax=INT      The lifetime in seconds of this metric  (default=`0')

Gmetric sends the metric specified on the commandline to all udp_send_channels specified -in the configuration file /etc/gmond.conf by default. If you want to send metric to +in the configuration file @PKG_SYSCONFDIR@/gmond.conf by default. If you want to send metric to alternate udp_send_channels, you can specify a different configuration file as such:

   % gmetric --conf=./custom.conf -n "wow" -v "it works" -t "string"

@@ -913,7 +913,7 @@ mcast_if eth1 - .. in /etc/gmond.conf that tells gmond to send its data out the "eth1" + .. in @PKG_SYSCONFDIR@/gmond.conf that tells gmond to send its data out the "eth1" network interface but that doesn't necessarily mean that the source address of the packets will match the "eth1" interface. to make sure that data sent out eth1 has the correct source address run the following... @@ -951,7 +951,7 @@ > 26 nodes each > gmond > - > In the frontend /etc/gmond.conf I have the + > In the frontend @PKG_SYSCONFDIR@/gmond.conf I have the > following statement: mcast_if eth1 > > The 26 nodes are correctly reported.