Caleb, Martin:
Any more discussions regarding this? If not, I would probably just
leave it as is and close the ticket (unless there is a strong reason
to switch).
P.S. How about having a configuration parameter to switch between the two?
Cheers,
Bernard
On 11/2/07, Martin Knoblauch <[EMAIL PR
Hi Matt and/or Martin:
I'd like to create a directory called 'snapshots' under htdocs so that
I could upload ganglia snapshot releases to the webpage -- would you
be able to help me create that dir?
Better yet, can you simply do a chgrp -R ganglia for htdocs and change
it to group writable?
Than
Hi Rick:
On 11/14/07, Richard Mohr <[EMAIL PROTECTED]> wrote:
> I think that looks good. I had actually debated whether the logic
> should go in the spec file or configure.in. I ended up modifying the
> spec file because I was more familiar with it than with the autoconf
> stuff, but your patch
Hi all:
I would like to propose that GANGLIA_SNAPSHOT in configure.in be
changed in "yes" in our code repository by default. This way when a
developer is checking code out of the repo, the build will always
produce a snapshot build.
When we make a release, then we change it to "no" (i.e. when we
I wrote a small bit of code in order to track aggregate system temperatures,
and tried to make use of the $optional_graphs feature. Doing so broke the pie
chart.
I tracked down the problem to the templating code, and the blocks used for
variable substitution. Basically, a new block is create