__pmconnectlogger(3) [centos man page]

PMCONNECTLOGGER(3)					     Library Functions Manual						PMCONNECTLOGGER(3)

NAME

       __pmConnectLogger - connect to a performance metrics logger control port

C SYNOPSIS

       #include <pcp/pmapi.h>
       #include <pcp/impl.h>

       int __pmConnectLogger(const char *hostname, int pid);

       cc ... -lpcp

DESCRIPTION

       Each  instance  of  the	Performance  Co-Pilot  (PCP) archive logger program pmlogger(1) supports a control port on which __pmControlLog(3)
       requests are received, and responses sent.  Optionally, the pmlogger(1) instance may be designated the ``primary'' logger.

       __pmConnectLogger may be used to establish a control port connection to the pmlogger(1) instance identified by process id pid on  the  host
       hostname.

       One  special  case  is supported; for the reserved pid value of PM_LOG_CONTROL_PORT the requested connection is to the control port for the
       ``primary'' logger, whatever its process id might be.

       On success, __pmConnectLogger returns a non-negative integer, that is a file descriptor that may be used in subsequent  communication  with
       the pmlogger(1) instance, e.g. for __pmControlLog(3).

       As the control port to pmlogger(1) is not mulitplexed, applications using __pmConnectLogger should use close(2) to terminate the connection
       to pmlogger(1) as soon as they have finished communicating.

       If the application connects, and the pmlogger(1) instance subsequently terminates, e.g. because the associated pmcd(1) instance	is  termi-
       nated,  the  application  will have to explicitly re-establish connection to a re-started pmlogger(1) instance by calling __pmConnectLogger
       again.

SEE ALSO

       pmcd(1), pmlc(1), pmlogger(1), PMAPI(3) and __pmControlLog(3).

DIAGNOSTICS

       PM_ERR_PERMISSION
	      no permission to connect to the specified pmlogger(1) instance

       -ECONNREFUSED
	      the designated pmlogger(1) instance does not exist

       -EEADDRINUSE
	      the requested control port is already in use

Performance Co-Pilot							PCP							PMCONNECTLOGGER(3)

PCP(1)							      General Commands Manual							    PCP(1)

NAME

       pcp - summarize a Performance Co-Pilot (PCP) installation

SYNOPSIS

       pcp [-p] [-a archive] [-h host] [-n pmnsfile]

DESCRIPTION

       The  pcp command summarizes the status of a Performance Co-Pilot (PCP) installation.  The report includes: the OS version, a summary of the
       hardware inventory, the local timezone, details of valid PCP licenses, the PCP software version, the state of the pmcd(1) process and asso-
       ciated  Performance  Metrics  Domain  Agents  (PMDAs), as well as information about any PCP archive loggers (pmlogger(1)) and PCP inference
       engines (pmie(1)) that are running.

       For more general information about PCP, refer to PCPIntro(1).

       With no arguments, pcp reports on the local host, however the following options are accepted:

       -a archive
	      Report the PCP configuration as described in the PCP archive log archive.

       -h host
	      Report the PCP configuration on host rather than the local host.

       -n pmnsfile
	      Load an alternative Performance Metrics Name Space (pmns(5)) from the file pmnsfile.

       -p     Display pmie performance information - counts of rules evaluating to true, false, or indeterminate, as well as the expected rate	of
	      rule  calculation,  for each pmie process running on the default host.  Refer to the individual metric help text for full details on
	      these values.

       All of the displayed values are performance metric values and further information for each can be obtained using the command:

	  $ pminfo -dtT metric

       The complete set of metrics required by pcp to produce its output is contained in $PCP_SYSCONF_DIR/pmlogger/config.pcp.

       When displaying running pmlogger instances, as a space-saving measure pcp will display a relative path to the archive being created if that
       archive is located below a pcplog subdirectory, otherwise the full pathname is displayed (the PCP log rotation and periodic pmlogger check-
       ing facilities support the creation of archives below $PCP_LOG_DIR/pmlogger/<hostname>).

       A similar convention is used for trimming the amount of information displayed for running pmie instances, where configuration  files  below
       $PCP_VAR_DIR/config will be displayed in truncated form.

FILES

       $PCP_SYSCONF_DIR/pmlogger/config.pcp
		 pmlogger configuration file for collecting all of the metrics required by pcp.

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).

SEE ALSO

       PCPIntro(1), pmcd(1), pmie(1), pmlogger(1), pcp.conf(5) and pcp.env(5).

DIAGNOSTICS

       pcp  will  terminate  with an exit status of 1 if pmcd on the target host could not be reached or the archive could not be opened, or 2 for
       any other error.

Performance Co-Pilot							PCP								    PCP(1)