An application using the Performance Metrics Application Programming
Interface (PMAPI) may manipulate several concurrent contexts, each
associated with a source of performance metrics, e.g. pmcd(1) on some
host, or an archive log of performance metrics as created by
pmDestroyContext destroys the PMAPI context identified by handle.
Typically this would imply some termination of a connection to a PMCD
or closing an archive log file, and orderly clean-up.
The context must have been previously created using pmNewContext(3)
On success, pmDestroyContext returns zero. If handle was the current
PMAPI context, then the current context becomes undefined. This
means the application must explicitly re-establish a valid PMAPI
context with pmUseContext(3), or create a new context with
pmNewContext(3) or pmDupContext(3), before the next PMAPI operation
that requires a PMAPI context.
This page is part of the PCP (Performance Co-Pilot) project.
Information about the project can be found at ⟨http://www.pcp.io/⟩.
If you have a bug report for this manual page, send it to
email@example.com. This page was obtained from the project's upstream
Git repository ⟨https://github.com/performancecopilot/pcp.git⟩ on
2020-08-13. (At that time, the date of the most recent commit that
was found in the repository was 2020-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 is not part of the original manual page), send a mail to
Performance Co-Pilot PCP PMDESTROYCONTEXT(3)