Hi Martin,
Nah, it's not really a problem.
In fact I think the way it works now may be better. It allows one to
include an entire section.
This way one can split up gmond.conf, in a global cluster conf and a
machine specific conf.
For example, include on each node the _host { location = "something"
}_part from a seperate config file, which is what I actually want to do.
Then from a maintainability perspective it is easier to generate the
host specific config (location) on each node, while keeping a global
cluster config that stays the same.
However, I could imagine that some people might just want to include 1
option from a section (i.e. mute or deaf for globals or something).
But I can imagine that implementing both behaviours can be tricky.
I will try to see if I can make a patch for the man page, but right now
I am drowning in work. ;)
Cheers,
- Ramon.
Martin Knoblauch wrote:
Hi Ramon,
you are right, the web page is wrong. I will fix that. "include" only
works from the top level in the gmond.conf file. This was discussed
briefly during the 3.0.2 period when we made include work at all.
Is that behaviour a problem? We could change it in 3.0.3, but is there
a real use-case?
As for the man page - PAW(tm) (Patches Are Welcome :-)
Cheers
Martin
--- Ramon Bastiaans <[EMAIL PROTECTED]> wrote:
Hey all,
It seems to me that the include() of extra configs does not work as
advertised on the website.
It only works from outside config sections.
