autofsd-probe(1) [centos man page]
AUTOFSD-PROBE(1) General Commands Manual AUTOFSD-PROBE(1) NAME
autofsd-probe - probe AutoFS mount/unmount daemon SYNOPSIS
$PCP_BINADM_DIR/autofsd-probe [-h host] [-t timeout] DESCRIPTION
autofsd-probe will check the status of the autofsd(1) daemon on the specified host. Unless directed to another host by the -h option, autofsd-probe will contact the AutoFS daemon on the local host. The AutoFS file system is built on the Remote Procedure Call (RPC(3)) library routines. The -t option allows the total timeout and retry timeout intervals to be set for all remote procedure call operations used with autofsd-probe. This option accepts an interval argument in the form described in the PCPintro(1) manual page. autofsd-probe is typically used in an automated fashion from within pmdashping(1) and in conjunction with pmie(1), for monitoring response time and service failure. By default autofsd-probe will not produce any output, unless there is an error in which case a diagnostic message will be displayed and the exit status will indicate the reason for failure. DIAGNOSTICS
If autofsd-probe succeeds, then 0 will be returned. If the attempt to establish a connection with autofsd fails, then 2 is returned. If the subsequent attempt to invoke an autofsd response fails, then 1 will be returned. In the case of a syntactical command line error, 4 is returned and the usage message is displayed. 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
autofs(1), autofsd(1), PCPintro(1), pmdashping(1), pmie(1) and RPC(3). Performance Co-Pilot PCP AUTOFSD-PROBE(1)
Check Out this Related Man Page
PMGETCONTEXTHOSTNAME(3) Library Functions Manual PMGETCONTEXTHOSTNAME(3) NAME
pmGetContextHostName - return the hostname associated with a Performance Co-Pilot context C SYNOPSIS
#include <pcp/pmapi.h> const char *pmGetContextHostName(int id); cc ... -lpcp DESCRIPTION
Given a valid PCP context identifier previously created with pmNewContext(3) or pmDupContext(3), the pmGetContextHostName function returns the hostname associated with id. If the context id is associated with an archive source of data, the hostname returned is extracted from the archive label using pmGetArchiveLabel(3). For live contexts, an attempt will first be made to retrieve the hostname from the PCP collector system using pmFetch(3) with the pmcd.hostname metric. This allows client tools using this interface to retrieve an accurate host identifier even in the presence of port forwarding and tunnelled connections. Should this not succeed, then a fallback method is used. For local contexts - with local meaning any of DSO, ``localhost'' or Unix domain socket connection - a hostname will be sought via gethostname(3). For other contexts, the hostname extracted from the initial context host specification will be used. RETURN VALUE
If id is not a valid PCP context identifier, this function returns a zero length string and hence never fails. 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
PCPIntro(1), PMAPI(3), gethostname(3), pmDupContext(3), pmFetch(3), pmGetArchiveLabel(3), pmNewContext(3), pcp.conf(5) and pcp.env(5). Performance Co-Pilot PCP PMGETCONTEXTHOSTNAME(3)