Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmpost(1) [centos man page]

PMPOST(1)						      General Commands Manual							 PMPOST(1)

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 man- ner 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. 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). SEE ALSO
pmie(1), pcp.conf(5) and pcp.env(5). Performance Co-Pilot PCP PMPOST(1)

Check Out this Related Man Page

PCP.CONF(5)							File Formats Manual						       PCP.CONF(5)

NAME
pcp.conf - the Performance Co-Pilot configuration and environment file SYNOPSIS
/etc/pcp.conf DESCRIPTION
When using Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables are defined in /etc/pcp.conf. These variables are generally used to specify the location of various PCP pieces in the file system and may be loaded into shell scripts by sourcing the /etc/pcp.env(5) shell script and queried by C/C++ programs using the pmGetConfig(3) library function. If a variable is already defined in the environment, the values in pcp.conf do not override those values, i.e. the values in pcp.conf serve as installation defaults only. Both the pcp.env and pcp.conf files are expected to be found in /etc by default. If required, the pcp.conf file may be relocated and PCP_CONF set in the environment to specify the full path to the new location. The pcp.env file can not be relocated (this is the only hard coded path required by PCP). The syntax rules for pcp.conf are as follows : 1. the general syntax is PCP_VARIABLE_NAME=variable value to end of line 2. lines that begin with # and all blank lines are ignored. 3. all variables must be prefixed with PCP_. This is a security issue - variables that do not have this prefix will be silently ignored. 4. there should be no space between the variable name and the literal = and no space between the = and the variable value (unless the value actually starts with a space). This is required because the pcp.conf file may be sourced directly by Makefiles as well as inter- preted by the pcp.env script and the pmGetConfig function. 5. variable values may contain spaces and should not be quoted. The pcp.env script automatically quotes all variable values from the character immediately following the = through to the end of the line. For further details and an explanation of the use of each variable, see the comments in the /etc/pcp.conf file itself. ENVIRONMENT
The PCP_CONF environment variable specifies an alternative path to the pcp.conf file. SEE ALSO
PCPIntro(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.env(5). Performance Co-Pilot PCP PCP.CONF(5)
Man Page