Provided by: pcp_3.5.11_amd64 bug

NAME

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

SYNOPSIS

       $PCP_BINADM_DIR/pmpost 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.  Due to the importance of
       the notice board file, pmpost is typically installed as a setuid(2) root  program  and  so
       the notice board is owned by, and writable only by, root.

FILES

       $PCP_LOG_DIR/NOTICES
                 the PCP notice board file

PCP ENVIRONMENT

       The  file  /etc/pcp.conf  contains the local values for PCP_ variables.  Because pmpost is
       setuid(1), only the settings in  /etc/pcp.conf  are  used.   In  addition,  the  $PCP_CONF
       variable may not be used to specify an alternative configuration file for pmpost.

UNIX SEE ALSO

       logger(1).

WINDOWS SEE ALSO

       pcp-eventlog(1).

SEE ALSO

       pmie(1), setuid(2), pcp.conf(4) and pcp.env(4).