When building ganglia as a FreeBSD port, I apply a number of patches and
run some sed scripts to deal with the fact that the following paths are
hardcoded into ganglia:
/etc/gmetad.conf
/etc/gmond.conf
/var/lib/ganglia/rrds
The problem with this is that FreeBSD ports expect to find their config
f
I know what you mean about the data forking as it relates to the hostname
and IP address, an example is where a set of gmonds are running and only a
pair of them have tcp port 8649 listening, and one of them has a custom
hosts file or certain knowledge of ip to hostname mapping that differs from
th
On Tue, Feb 24, 2004 at 12:10:35PM -0800, Matt Massie wrote:
> if we simply key on ip address, it would cause other problems. when you
> remap ip/hostname pairs in a network overhaul.. it's very possible to
> have ip gets swapped (not just changed for a single host). in that case
> the data forks
the real problem here is not that data will be lost if the ip/hostname
pair changes. the real problem is that the data forks to two different
places.
gmetad is currently not smart enough to know that a fork occurred. i
don't see a simple way to make it smart.
here's one way...
gmetad saves a d
On Tue, Feb 24, 2004 at 09:06:10AM +0100, Leif Nixon wrote:
> Brooks Davis <[EMAIL PROTECTED]> writes:
>
> > Since this will require a conversion script anyway, would it be
> > possiable to move away from using hostnames in the data store entierly?
> > It has the weird effect that if you don't hav
Brooks Davis <[EMAIL PROTECTED]> writes:
> Since this will require a conversion script anyway, would it be
> possiable to move away from using hostnames in the data store entierly?
> It has the weird effect that if you don't have a hosts entry in
> place the first time the host comes on, it gets s
