On 06/07/13 14:03, Ken McDonell wrote:
...
Anyway, the real issue here is commit dc62541 that added pmlogconf to
pmlogger_check.sh ...
Upon further investigation it appears that my initial analysis was not
quite correct, although the end result of a radically changed pmlogger
configuration remains the same.
Let's start with the control line for the host foo
foo n n PCP_LOG_DIR/pmlogger/foo -c ./config.foo
now pmlogger is launched in the PCP_LOG_DIR/pmlogger/foo directory and
interprets the -c option as follows:
If ./config.foo does not exist, then a search is made in the
directory $PCP_SYSCONF_DIR/pmlogger for a file of the same
name, and if found that file is used,
In my setup, config.foo was in $PCP_SYSCONF_DIR/pmlogger.
So when the new pmlogger_check needs to start a pmlogger, and apparently
only checks in $PCP_LOG_DIR/pmlogger/foo sees there is no config.foo and
so it creates one using pmlogconf with all the default values.
Rather than clobbering my config.foo as I had assumed, pmlogger_check
has installed a new config.foo that pmlogger uses in lieu of my
customized one.
|