HTML rendering created 2025-09-06 byMichael Kerrisk, author ofThe Linux Programming Interface. For details of in-depthLinux/UNIX system programming training courses that I teach, lookhere. Hosting byjambit GmbH. |  |
NAME |C SYNOPSIS |DESCRIPTION |CAVEAT |DIAGNOSTICS |SEE ALSO |COLOPHON | |
PMDADAEMON(3) Library Functions ManualPMDADAEMON(3)pmdaDaemon- initialize the PMDA to run as a daemon
#include <pcp/pmapi.h>#include <pcp/pmda.h>void pmdaDaemon(pmdaInterface *dispatch, intinterface,const char *name, intdomain, const char *logfile,const char *helptext);cc ... -lpcp_pmda -lpcp
pmdaDaemoninitializes thepmdaInterfacestructure to use thein‐terface extensions assuming thePMDA(3) is to be run as a daemon. ThepmdaInterfacestructure is initialized with:name The name of the agent.domain The default domain number of the agent which uniquely iden‐ tifies this PMDA from other running PMDAs. This may be subsequently changed by a command line option-d(seepmdaGetOpt(3)).logfile The default path to the log file. This may be replaced by the-lcommand line option if usingpmdaGetOpt.logfile will be copied withstrdup(3), so the storage associated withlogfile may be released after the call topmdaDaemon.helptext The default path to the help text (seepmdaText(3). This may be replaced by the-hcommand line option if usingpmdaGetOpt(3). If no help text is installed, or you are not usingpmdaText(3), then this should be set to NULL, otherwisehelptext will be copied withstrdup(3), so the storage associated withhelptext may be released after the call topmdaDaemon. The callbacks are initialized topmdaProfile(3),pmdaFetch(3),pmdaDesc(3),pmdaText(3),pmdaInstance(3) andpmdaStore(3).
The PMDA must be usingPMDA_INTERFACE_2or later. OncepmdaDaemonhas been called, it is expected that thepmdaIn‐terfacestructure pointed to bydispatch will remain accessible to the routines inlibpcp_pmda (not reclaimed off the stack, not freed or otherwise released, etc.). If the caller needs to move or relocate thepmdaInterfacestructure for any reason, then after the movepmdaInterfaceMoved(3) must be called to re-establish the internal integrity of thepmdaInterface structure at the new loca‐ tion before any other routine inlibpcp_pmda is called.
Unable to allocate memory for pmdaExt structure In addition, thedispatch->status field is set to a value less than zero.PMDA interface versioninterfacenot supported Theinterface version is not supported bypmdaDaemon.
PMAPI(3),PMDA(3),pmdaDSO(3),pmdaGetOpt(3),pmdaInterfaceMoved(3) andpmdaText(3).
This page is part of thePCP (Performance Co-Pilot) project. In‐ formation about the project can be found at ⟨http://www.pcp.io/⟩. If you have a bug report for this manual page, send it to pcp@groups.io. This page was obtained from the project's upstream Git repository ⟨https://github.com/performancecopilot/pcp.git⟩ on 2025-08-11. (At that time, the date of the most recent commit that was found in the repository was 2025-08-11.) If you discover any rendering problems in this HTML version of the page, or you believe there is a better or more up-to-date source for the page, or you have corrections or improvements to the information in this COLOPHON (which isnot part of the original manual page), send a mail to man-pages@man7.orgPerformance Co-Pilot PCPPMDADAEMON(3)Pages that refer to this page:pmda(3), pmdaattribute(3), pmdachildren(3), pmdaconnect(3), pmdadesc(3), pmdadso(3), pmdafetch(3), pmdagetoptions(3), pmdahelp(3), pmdainit(3), pmdainstance(3), pmdainterfacemoved(3), pmdalabel(3), pmdaname(3), pmdaopenlog(3), pmdapmid(3), pmdaprofile(3), pmdastore(3), pmdatext(3)
HTML rendering created 2025-09-06 byMichael Kerrisk, author ofThe Linux Programming Interface. For details of in-depthLinux/UNIX system programming training courses that I teach, lookhere. Hosting byjambit GmbH. | |