pmreconnectcontext(3) [centos man page]

PMRECONNECTCONTEXT(3)					     Library Functions Manual					     PMRECONNECTCONTEXT(3)

NAME

       pmReconnectContext - reconnect to a PMAPI context

C SYNOPSIS

       #include <pcp/pmapi.h>

       int pmReconnectContext(int handle);

       cc ... -lpcp

DESCRIPTION

       As  a  consequence  of  network,  host or Performance Metrics Collector Daemon (PMCD) failures, an applications connection to a PMCD may be
       established and then subsequently lost.

       The routine pmReconnectContext allows an application to request that the context identified by handle should  be  re-established,  provided
       the associated PMCD is accessible.

       To  avoid  flooding the system with reconnect requests, pmReconnectContext will only attempt a reconnection after a suitable delay from the
       previous unsuccessful attempt to reconnect this context. This imposed restriction on the reconnect re-try time interval uses an exponential
       back-off so that the initial delay is 5 seconds after the first unsuccessful attempt, then 10 seconds, then 20 seconds, then 40 seconds and
       then 80 seconds thereafter.

       The environment variable PMCD_RECONNECT_TIMEOUT may be used to redefine the back-off intervals, see PMAPI(3).

       If the reconnection succeeds, pmReconnectContext returns handle.

       If handle identifies a context associated with an archive source of metrics, pmReconnectContext does nothing and returns handle.

       Calling pmReconnectContext with a handle identifying a currently connected context will cause the connection to be broken before any recon-
       nection is attempted.

       Note  that  even  in  the case of a successful reconnection, pmReconnectContext does not change the current Performance Metrics Application
       Programming Interface (PMAPI) context.

       When attempting to connect to a remote pmcd(1) on a machine that is booting, pmReconnectContext could potentially block	for  a	long  time
       until  the  remote  machine  finishes its initialization.  pmReconnectContext will abort and return an error if the connection has not been
       established after some specified interval has elapsed.  The default interval is 5 seconds.  This  may  be  modified  by	setting  PMCD_CON-
       NECT_TIMEOUT in the environment to a real number of seconds for the desired timeout.  This is most useful in cases where the remote host is
       at the end of a slow network, requiring longer latencies to establish the connection correctly.

ENVIRONMENT

       PMCD_CONNECT_TIMEOUT
	      Timeout period (in seconds) for pmcd(1) connection attempts.

       PMCD_RECONNECT_TIMEOUT
	      Redefines the back-off intervals - refer to PMAPI(3).

SEE ALSO

       pmcd(1), PMAPI(3), pmNewContext(3) and pmUseContext(3).

DIAGNOSTICS

       PM_ERR_NOCONTEXT

	      handle does not identify a valid PMAPI context

       -ETIMEDOUT

	      The re-try time has not elapsed, or the reconnection is attempted and fails.

CAVEAT

       Applications that use gethostbyname(3) should exercise caution because the static fields in struct hostent may not be preserved across some
       PMAPI(3) calls.	In particular, pmNewContext(3) and pmReconnectContext(3) both may call gethostbyname(3) internally.

Performance Co-Pilot							PCP						     PMRECONNECTCONTEXT(3)

Check Out this Related Man Page

PMDACONNECT(3)						     Library Functions Manual						    PMDACONNECT(3)

NAME

       pmdaConnect - establish a connection between a daemon PMDA and PMCD

C SYNOPSIS

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

       void pmdaConnect(pmdaInterface *dispatch);

       cc ... -lpcp_pmda -lpcp

DESCRIPTION

       pmdaConnect  initializes  an IPC channel between a PMDA(3) and the pmcd(1) process on the local host.  The type of the connection is depen-
       dent on the e_io field of the pmdaExt structure:

       pmdaPipe       Use stdin/stdout to communicate; assumes this is a pipe created by pmcd before the PMDA(3) was launched.

       pmdaInet       Assume pmcd(1) will establish a connection to an IPv4 internet domain socket set up by the PMDA(3).  The name or	number	of
		      the port must be specified in the e_sockname or e_port fields of the pmdaExt structure, respectively.

       pmdaIPv6       Assume  pmcd(1)  will establish a connection to an IPv6 internet domain socket set up by the PMDA(3).  The name or number of
		      the port must be specified in the e_sockname or e_port fields of the pmdaExt structure, respectively.

       pmdaUnix       Assume pmcd(1) will establish a connection to a unix domain socket set up by the PMDA(3).  The port number must be specified
		      in the e_port field of the pmdaExt structure.

       pmdaUnknown    The initial value of e_io which defaults to using stdin/stdout.

       The  relevant  pmdaExt  fields  are  initialized by pmdaInit(3) and set by pmdaGetOpt(3), so most PMDAs should not need to access or modify
       them.

DIAGNOSTICS

       pmdaConnect will log the type of connection made to pmcd(1) if the PMAPI(3) debug control variable (pmDebug) has the DBG_TRACE_LIBPMDA flag
       set.

       If an error occurs that is unrecoverable, dispatch->status is set to a value less than 0, otherwise it is zero or positive.

CAVEAT

       The PMDA must be using PMDA_INTERFACE_2 or later, as specified in the call to pmdaDaemon(3).

SEE ALSO

       pmcd(1), pipe(2), socket(2), PMAPI(3), PMDA(3), pmdaDaemon(3), pmdaGetOpt(3) and pmdaInit(3).

Performance Co-Pilot							PCP							    PMDACONNECT(3)

Linux and UNIX Man Pages

pmreconnectcontext(3) [centos man page]

Check Out this Related Man Page