NAME¶

pmpost - append messages to the Performance Co-Pilot notice board

SYNOPSIS¶

$PCP_BINADM_DIR/pmpost [-D debug] message

DESCRIPTION¶

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 and writable by the $PCP_USER user, and readable by others.

FILES¶

$PCP_LOG_DIR/NOTICES

the PCP notice board file

PCP ENVIRONMENT¶

The file /etc/pcp.conf contains the local values for PCP_ variables.

UNIX SEE ALSO¶

logger(1).

WINDOWS SEE ALSO¶

pcp-eventlog(1).

DEBUGGING OPTIONS¶

The -D or --debug option enables the output of additional diagnostics on stderr to help triage problems, although the information is sometimes cryptic and primarily intended to provide guidance for developers rather end-users. debug is a comma separated list of debugging options; use pmdbg(1) with the -l option to obtain a list of the available debugging options and their meaning.

SEE ALSO¶

pmie(1), pcp.conf(5) and pcp.env(5).