Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pcp.conf(5) [centos man page]

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

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)

Check Out this Related Man Page

PMDISCOVERSERVICES(3)					     Library Functions Manual					     PMDISCOVERSERVICES(3)

pmDiscoverServices - discover PCP services on the network C SYNOPSIS
#include <pcp/pmapi.h> int pmDiscoverServices(const char *service, const char *mechanism, char ***urls); cc ... -lpcp DESCRIPTION
Given a PCP service name, as identified by service, and using the type of discovery optionally specified in mechanism, pmDiscoverServices returns, via urls, a list of URLs representing the services discovered on the network. service specifies the PCP service to be discovered. Currently, only PM_SERVER_SERVICE_SPEC is supported, which searches for pmcd(1) servers. mechanism specifies the style of discovery to be used. Currently, only "avahi" is supported. This searches for services which are broad- casting using mDNS via avahi-daemon(8). mechanism may also be NULL, which means to use all available discovery mechanisms. Normally, pmDiscoverServices will return the number of services discovered, else a value less than zero for an error. The value zero indi- cates that no services were discovered. The resulting list of pointers, urls, and the values (the URLs) that the pointers reference will have been allocated by pmDiscoverServices with a single call to malloc(3C), and it is the responsibility of the pmDiscoverServices caller to free(urls) to release the space when it is no longer required. When an error occurs, or no services are discovered, urls is undefined (no space will have been allocated, and so calling free(3C) is a singularly bad idea). 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). Values for these variables may be obtained programmatically using the pmGetConfig(3) function. SEE ALSO
PMAPI(3), pmcd(1), pmfind(1), pmGetConfig(3), pcp.conf(5), pcp.env(5) and avahi-daemon(8). DIAGNOSTICS
EOPNOTSUPP The specified mechanism is not supported. Performance Co-Pilot PCP PMDISCOVERSERVICES(3)
Man Page

Featured Tech Videos