pmfind(1) [centos man page]

PMFIND(1)						      General Commands Manual							 PMFIND(1)

NAME

       pmfind - find PCP services on the network

SYNOPSIS

       pmfind [-q] [-m mechanism] [-s service]

DESCRIPTION

       pmfind  searches  for instances of the specified PCP service being advertised on the network and prints a list of URLs corresponding to the
       services discovered.

       By default pmfind will search for servers advertising the pmcd(1) service, however an alternate PCP service to discover	can  be  specified
       using the -s option.

       The  -m	option	sets  the mechanism that pmfind uses when performing service discovery.  By default, or if the keyword "all" is specified,
       every available mechanism will be used (iteratively).  Currently, "avahi" is the only supported discovery mechanism.

       The -q option suppresses all output on the standard output stream.

PCP ENVIRONMENT

       Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP.  On  each	installation,  the
       file  /etc/pcp.conf contains the local values for these variables.  The $PCP_CONF variable may be used to specify an alternative configura-
       tion file, as described in pcp.conf(5).

DIAGNOSTICS

       The value of the exit status from the command is zero when services were successfully located, one if no services were found, and two if an
       error occurred.

       In the event of an error, a message will be generated on standard error that is intended to be self-explanatory.

SEE ALSO

       PCPIntro(1), pmcd(1), PMAPI(3), pmDiscoverServices(3), pcp.conf(5) and pcp.env(5).

Performance Co-Pilot							PCP								 PMFIND(1)

PCP.CONF(5)							File Formats Manual						       PCP.CONF(5)

NAME

       pcp.conf - the Performance Co-Pilot configuration and environment file

SYNOPSIS

       /etc/pcp.conf

DESCRIPTION

       When  using  Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables
       are defined in /etc/pcp.conf.  These variables are generally used to specify the location of various PCP pieces in the file system and  may
       be  loaded  into  shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library
       function.  If a variable is already defined in the environment, the values in pcp.conf do not override those values,  i.e.  the	values	in
       pcp.conf serve as installation defaults only.

       Both  the  pcp.env  and	pcp.conf  files  are expected to be found in /etc by default.  If required, the pcp.conf file may be relocated and
       PCP_CONF set in the environment to specify the full path to the new location.  The pcp.env file can not be relocated (this is the only hard
       coded path required by PCP).

       The syntax rules for pcp.conf are as follows :

       1.  the general syntax is
						       PCP_VARIABLE_NAME=variable value to end of line

       2.  lines that begin with # and all blank lines are ignored.

       3.  all variables must be prefixed with PCP_.  This is a security issue - variables that do not have this prefix will be silently ignored.

       4.  there  should  be  no  space  between the variable name and the literal = and no space between the = and the variable value (unless the
	   value actually starts with a space).  This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter-
	   preted by the pcp.env script and the pmGetConfig function.

       5.  variable  values  may  contain  spaces  and should not be quoted.  The pcp.env script automatically quotes all variable values from the
	   character immediately following the = through to the end of the line.

       For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself.

ENVIRONMENT

       The PCP_CONF environment variable specifies an alternative path to the pcp.conf file.

SEE ALSO

       PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5).

Performance Co-Pilot							PCP							       PCP.CONF(5)