Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #361
Difficulty: Medium
The rmdir command remove directories, even if they are not empty.
True or False?
Linux & Unix Commands - Search Man Pages

pmdiscoverservices(3) [centos man page]

PMDISCOVERSERVICES(3)					     Library Functions Manual					     PMDISCOVERSERVICES(3)

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

Check Out this Related Man Page

PMGETCONFIG(3)						     Library Functions Manual						    PMGETCONFIG(3)

NAME
pmGetConfig - return Performance Co-Pilot configuration variable C SYNOPSIS
#include <pcp/pmapi.h> char *pmGetConfig(const char *variable); #include <pcp/impl.h> char *__pmGetAPIConfig(const char *feature); cc ... -lpcp DESCRIPTION
The pmGetConfig function searches for variable first in the environment and then, if not found, in the Performance Co-Pilot (PCP) configu- ration file and returns the string result. If variable is not already in the environment, it is added with a call to putenv(3) before returning. The default location of the PCP configuration file is /etc/pcp.conf but this may be changed by setting PCP_CONF in the environment to a new location, as described in pcp.conf(5). The internal __pmGetAPIConfig function reports on features of the PCP library. It can be used to query support for multi-threading, secu- rity extensions, and other features. The pmconfig(1) utility provides command line access to both of these interfaces, and also provides a mechanism for listing all available variables and features that are valid arguments to these routines. RETURN VALUE
If variable is not found in either the environment nor the PCP configuration file then the return value is an empty string. If the PCP configuration file is not found then a fatal error message is printed and the process will exit(2) - although this sounds drastic, it is the only course of action available because the PCP configuration/installation is fatally flawed. If the pmGetConfig function returns a non-empty string, the returned value points into the environment and so changing it is a bad idea. This function returns the same type as the getenv(3) function (which should probably be a const char *). The __pmGetAPIConfig routine on the other hand returns NULL on failure to lookup the requested feature. It does not modify the environ- ment, and returns a pointer to a static read-only string which also should not be modified or freed by the caller. 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), pmconfig(1), exit(2), PMAPI(3), getenv(3C), putenv(3C), pcp.conf(5), pcp.env(5) and environ(5). Performance Co-Pilot PCP PMGETCONFIG(3)

Featured Tech Videos