blob: 2dcfd1fba0f1a149aa995b9a29de063133719f15 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
|
#
# PCP inference engine configuration/control
#
# This file is used by a number of the PCP inference engine administrative
# tools to perform maintenance on the pmie instances running on the local host.
#
# This file contains one line per host to be monitored, fields are
# Host name of host to be monitored
# S(ocks)? should this pmie be launched with pmsocks? y or n
# Log File full pathname to file where pmie activity log is to be
# maintained ... note all scripts "cd" the directory housing
# this file as a first step
# Arguments optional additional arguments to pmie
#
# === VARIABLE ASSIGNMENTS ===
#
$version=1.0
# if pmsocks is being used, edit the IP address for $SOCKS_SERVER and
# uncomment the next line
#$SOCKS_SERVER=123.456.789.123; export SOCKS_SERVER
# if remote pmie instances are run over a WAN with potentially long delays,
# adjust the following and uncomment
#$PMCD_CONNECT_TIMEOUT=20; export PMCD_CONNECT_TIMEOUT
#$PMCD_REQUEST_TIMEOUT=15; export PMCD_REQUEST_TIMEOUT
# === PMIE CONTROL SPECIFICATIONS ===
#
# Note: - if multiple pmie instances for the same host, then they MUST use
# different log files;
# - any occurence of LOCALHOSTNAME will be replaced by local hostname;
# - pmie's configuration file search path is "./:$PCP_SYSCONF_DIR/pmie/",
# and the working directory ('.') is the dirname of the Log File.
#
#Host S? Log File Arguments
LOCALHOSTNAME n PCP_LOG_DIR/pmie/LOCALHOSTNAME/pmie.log -c config.default
# remote host
#remote n PCP_LOG_DIR/pmie/remote/pmie.log -c config.remote
# thru the firewall via socks
#distant y PCP_LOG_DIR/pmie/distant/pmie.log -c config.distant
|
