PMPOST(1) General Commands Manual PMPOST(1)
pmpost - append messages to the Performance Co-Pilot notice board
pmpost will append the text message to the end of the Performance Co- Pilot (PCP) notice board file ($PCP_LOG_DIR/NOTICES) in an atomic manner that guards against corruption of the notice board file by concurrent invocations of pmpost. The PCP notice board is intended to be a persistent store and clearing house for important messages relating to the operation of the PCP and the notification of performance alerts from pmie(1) when other notification options are either unavailable or unsuitable. Before being written, messages are prefixed by the current time, and when the current day is different to the last time the notice board file was written, pmpost will prepend the message with the full date. If the notice board file does not exist, pmpost will create it. pmpost would usually run from long-running PCP daemons executing under the (typically unprivileged) $PCP_USER and $PCP_GROUP accounts. The file should be owned by root, and group writable by the $PCP_GROUP group.
$PCP_LOG_DIR/NOTICES the PCP notice board file
The file /etc/pcp.conf contains the local values for PCP_ variables.
pmie(1), pcp.conf(5) and pcp.env(5).
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 firstname.lastname@example.org. This page was obtained from the project's upstream Git repository ⟨git://git.pcp.io/pcp⟩ on 2017-04-25. 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 email@example.com Performance Co-Pilot PCP PMPOST(1)
Pages that refer to this page: pcpintro(1)