rvernica wrote:
> I have pmlogger collect logs from multiple hosts. My control file looks
> something like this:
>
> LOCALHOSTNAME y n PCP_LOG_DIR/pmlogger/LOCALHOSTNAME -r -T24h10m -c
> config.server
>
> b-01 n n PCP_LOG_DIR/pmlogger/b-01 -r -T24h10m -c config.remote
> b-02 n n PCP_LOG_DIR/pmlogger/b-02 -r -T24h10m -c config.remote
> b-03 n n PCP_LOG_DIR/pmlogger/b-03 -r -T24h10m -c config.remote
> b-12 n n PCP_LOG_DIR/pmlogger/b-12 -r -T24h10m -c config.remote
> b-13 n n PCP_LOG_DIR/pmlogger/b-13 -r -T24h10m -c config.remote
> b-14 n n PCP_LOG_DIR/pmlogger/b-14 -r -T24h10m -c config.remote
> [...]
For comparison, if you were to use pmmgr to manage the remote pmloggers,
you could drop those lines from the pmlogger/control file, and instead:
(If you already have a config.remote file you like, first do:
# echo '-c /path/to/config.remote' > /etc/pcp/pmmgr/pmlogger
# rm -f /etc/pcp/pmmgr/pmlogconf
)
# cat >/etc/pcp/pmmgr/target-host
b-01
b-02
b-03
...
^D
# service pmmgr start
It'll work whether each b* host is up or down, responding within
seconds, not 30 minutes, of state changes.
- FChE
|