home *** CD-ROM | disk | FTP | other *** search
PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) NNNNAAAAMMMMEEEE PPPPCCCCPPPPIIIInnnnttttrrrroooo - introduction to the Performance Co-Pilot (PCP) IIIINNNNTTTTRRRROOOODDDDUUUUCCCCTTTTIIIIOOOONNNN Performance Co-Pilot (PCP) is an SGI product designed for monitoring and managing system-level performance. These services are distributed and scalable to accommodate the most complex system configurations and performance problems. From the perspective of package installation managers (such as iiiinnnnsssstttt(1) on IRIX and rrrrppppmmmm(1) on Linux), PCP is composed of two products. On Linux the products are: _P_C_P _C_o_l_l_e_c_t_o_r This is the part of PCP that collects and extracts performance data from various sources, e.g. the Linux /proc pseudo filesystem. It is available under GPL/LPGL from oss.sgi.com/projects/pcp. _P_C_P _M_o_n_i_t_o_r This is the part of PCP that displays data collected from hosts (or archives) that have the _P_C_P _C_o_l_l_e_c_t_o_r installed. On Irix the products are: _p_c_p__e_o_e For IRIX 6.5, this is included in the IRIX CD set. For other IRIX versions, this comes from the PCP product distribution. _p_c_p From the PCP product distribution This manual entry describes the high-level features and options common to the images within both products on each platform. OOOOVVVVEEEERRRRVVVVIIIIEEEEWWWW The PCP architecture is distributed in the sense that any PCP tool may be executing remotely. On the host (or hosts) being monitored, each domain of performance metrics, whether IRIX, a service layer, a database management system, a web server, an application, etc. requires a Performance Metrics Domain Agent (PMDA) which is responsible for collecting performance measurements from that domain. All PMDAs are controlled by the Performance Metrics Collector Daemon (ppppmmmmccccdddd(1)) on the same host. Client applications (the monitoring tools) connect to ppppmmmmccccdddd(1), which acts as a router for requests, by forwarding requests to the appropriate PMDA and returning the responses to the clients. Clients may also access performance data from a PCP archive (created using ppppmmmmllllooooggggggggeeeerrrr(1)) for retrospective analysis. PPPPaaaaggggeeee 1111 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) The following performance monitoring applications may be launched directly from the command line, or from the PPPPeeeerrrrffffTTTToooooooollllssss page of the IRIX Interactive Desktop (trademark) Icon Catalog. Each tool or command is documented completely in its own reference page. oooovvvviiiieeeewwww Displays a three-dimensional visualization of the topology and performance of an Origin system. ppppmmmmkkkkssssttttaaaatttt Outputs an ASCII high-level summary of system performance. ppppmmmmiiiieeee An inference engine that can evaluate predicate-action rules to perform alarms and automate system management tasks. ppppmmmmeeeemmmm ASCII report of memory usage by process. ppppmmmmiiiinnnnffffoooo Interrogate specific performance metrics and the meta data that describes them. ppppmmmmllllooooggggggggeeeerrrr Generates PCP archives of performance metrics suitable for replay by most PCP tools. ppppmmmmvvvvaaaallll Simple periodic reporting for some or all instances of a performance metric. If the PCP product is installed (along with the associated valid PCP licenses) then the following additional tools are available. ppppmmmmcccchhhhaaaarrrrtttt Displays trends over time of arbitrarily selected performance metrics from one or more hosts. oooossssvvvviiiissss Displays a three-dimensional bar chart of high-level CPU, disk, memory and network activity. mmmmppppvvvviiiissss Displays a three-dimensional bar chart of multiprocessor CPU utilization. ddddkkkkvvvviiiissss Displays a three-dimensional bar chart showing activity in the disk subsystem. ppppmmmmggggssssyyyyssss Displays a system-level visual monitor of a single host. PPPPaaaaggggeeee 2222 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) nnnnffffssssvvvviiiissss Displays a three-dimensional bar chart of Network File System (NFS) client and server activity. ppppmmmmdddduuuummmmpppptttteeeexxxxtttt Produce ASCII reports for arbitrary combinations of performance metrics. CCCCOOOOMMMMMMMMOOOONNNN CCCCOOOOMMMMMMMMAAAANNNNDDDD LLLLIIIINNNNEEEE AAAARRRRGGGGUUUUMMMMEEEENNNNTTTTSSSS There is a set of common command line arguments that are used consistently by most PCP tools. ----aaaa _a_r_c_h_i_v_e Performance metric information is retrospectively retrieved from the Performance Co-Pilot (PCP) _a_r_c_h_i_v_e, previously generated by ppppmmmmllllooooggggggggeeeerrrr(1). The ----aaaa and ----hhhh options are mutually exclusive. ----aaaa _a_r_c_h_i_v_e[,,,,_a_r_c_h_i_v_e,,,,...] An alternate form of ----aaaa for applications that are able to handle multiple archives. ----hhhh _h_o_s_t_n_a_m_e Unless directed to another host by the ----hhhh option, or to an archive by the ----aaaa option, the source of performance metrics will be the Performance Metrics Collector Daemon (PMCD) on the local host. The ----aaaa and ----hhhh options are mutually exclusive. ----nnnn _p_m_n_s_f_i_l_e Normally the distributed Performance Metrics Name Space (PMNS) is used, however if the ----nnnn option is specified an alternative local PMNS is loaded from the file _p_m_n_s_f_i_l_e. ----ssss _s_a_m_p_l_e_s The argument _s_a_m_p_l_e_s defines the number of samples to be retrieved and reported. If _s_a_m_p_l_e_s is 0 or ----ssss is not specified, the application will sample and report continuously (in real time mode) or until the end of the PCP archive (in archive mode). ----zzzz Change the reporting timezone to the local timezone at the host that is the source of the performance metrics, as identified via either the ----hhhh or ----aaaa options. ----ZZZZ _t_i_m_e_z_o_n_e By default, applications report the time of day according to the local timezone on the system where the application is executed. The ----ZZZZ option changes the timezone to _t_i_m_e_z_o_n_e in the format of the environment variable TTTTZZZZ as described in eeeennnnvvvviiiirrrroooonnnn(5). IIIINNNNTTTTEEEERRRRVVVVAAAALLLL SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN AAAANNNNDDDD AAAALLLLIIIIGGGGNNNNMMMMEEEENNNNTTTT Most PCP tools operate with periodic sampling or reporting, and the ----tttt and ----AAAA options may be used to control the duration of the sample interval and the alignment of the sample times. PPPPaaaaggggeeee 3333 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) ----tttt _i_n_t_e_r_v_a_l Set the update or reporting interval. The _i_n_t_e_r_v_a_l argument is specified as a sequence of one or more elements of the form _n_u_m_b_e_r[_u_n_i_t_s] where _n_u_m_b_e_r is an integer or floating point constant (parsed using ssssttttrrrrttttoooodddd(3C)) and the optional _u_n_i_t_s is one of: sssseeeeccccoooonnnnddddssss, sssseeeeccccoooonnnndddd, sssseeeeccccssss, sssseeeecccc, ssss, mmmmiiiinnnnuuuutttteeeessss, mmmmiiiinnnnuuuutttteeee, mmmmiiiinnnnssss, mmmmiiiinnnn, mmmm, hhhhoooouuuurrrrssss, hhhhoooouuuurrrr, hhhh, ddddaaaayyyyssss, ddddaaaayyyy and dddd. If the _u_n_i_t is empty, sssseeeeccccoooonnnndddd is assumed. In addition, the upper case (or mixed case) version of any of the above is also acceptable. Spaces anywhere in the _i_n_t_e_r_v_a_l are ignored, so 4444 ddddaaaayyyyssss 6666 hhhhoooouuuurrrrssss 33330000 mmmmiiiinnnnuuuutttteeeessss, 4444ddddaaaayyyy6666hhhhoooouuuurrrr33330000mmmmiiiinnnn, 4444dddd6666hhhh33330000mmmm and 4444dddd6666....5555hhhh are all equivalent. Multiple specifications are additive, e.g. ``1111hhhhoooouuuurrrr 11115555mmmmiiiinnnnssss 33330000sssseeeeccccssss'' is interpreted as 3600+900+30 seconds. ----AAAA _a_l_i_g_n By default samples are not necessarily aligned on any natural unit of time. The ----AAAA option may be used to force the initial sample to be aligned on the boundary of a natural time unit. For example ----AAAA 1111sssseeeecccc, ----AAAA 33330000mmmmiiiinnnn and ----AAAA 1111hhhhoooouuuurrrr specify alignment on whole seconds, half and whole hours respectively. The _a_l_i_g_n argument follows the syntax for an _i_n_t_e_r_v_a_l argument described above for the ----tttt option. Note that alignment occurs by advancing the time as required, and that ----AAAA acts as a modifier to advance both the start of the time window (see the next section) and the origin time (if the ----OOOO option is specified). TTTTIIIIMMMMEEEE WWWWIIIINNNNDDDDOOOOWWWW SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNN Many PCP tools are designed to operate in some time window of interest, e.g. to define a termination time for real-time monitoring or to define a start and end time within a PCP archive log. In the absence of the ----OOOO and ----AAAA options to specify an initial sample time origin and time alignment (see above), the PCP application will retrieve the first sample at the start of the time window. The following options may be used to specify a time window of interest. ----SSSS _s_t_a_r_t_t_i_m_e By default the time window commences immediately in real-time mode, or coincides with time at the start of the PCP archive log in archive mode. The ----SSSS option may be used to specify a later time for the start of the time window. PPPPaaaaggggeeee 4444 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) The _s_t_a_r_t_t_i_m_e parameter may be given in one of three forms (_i_n_t_e_r_v_a_l is the same as for the ----tttt option as described above, _c_t_i_m_e is described below): _i_n_t_e_r_v_a_l To specify an offset from the current time (in real-time mode) or the beginning of a PCP archive (in archive mode) simply specify the interval of time as the argument. For example ----SSSS 33330000mmmmiiiinnnn will set the start of the time window to be exactly 30 minutes from now in real-time mode, or exactly 30 minutes from the start of a PCP archive. -_i_n_t_e_r_v_a_l To specify an offset from the end of a PCP archive log, prefix the _i_n_t_e_r_v_a_l argument with a minus sign. In this case, the start of the time window precedes the time at the end of archive by the given interval. For example ----SSSS ----1111hhhhoooouuuurrrr will set the start of the time window to be exactly one hour before the time of the last sample in a PCP archive log. @_c_t_i_m_e To specify the calendar date and time (local time in the reporting timezone) for the start of the time window, use the ccccttttiiiimmmmeeee(3C) syntax preceded by an at sign. For example ----SSSS ''''@@@@ MMMMoooonnnn MMMMaaaarrrr 4444 11113333::::00007777::::44447777 1111999999996666'''' ----TTTT _e_n_d_t_i_m_e By default the end of the time window is unbounded (in real-time mode) or aligned with the time at the end of a PCP archive log (in archive mode). The ----TTTT option may be used to specify an earlier time for the end of the time window. The _e_n_d_t_i_m_e parameter may be given in one of three forms (_i_n_t_e_r_v_a_l is the same as for the ----tttt option as described above, _c_t_i_m_e is described below): _i_n_t_e_r_v_a_l To specify an offset from the start of the time window simply use the interval of time as the argument. For example ----TTTT 2222hhhh33330000mmmm will set the end of the time window to be 2 hours and 30 minutes after the start of the time window. -_i_n_t_e_r_v_a_l To specify an offset back from the time at the end of a PCP archive log, prefix the _i_n_t_e_r_v_a_l argument with a minus sign. For example ----TTTT ----99990000mmmm will set the end of the time window to be 90 minutes before the time of the last sample in a PCP archive log. @_c_t_i_m_e To specify the calendar date and time (local time in the reporting timezone) for the end of the time window, use the PPPPaaaaggggeeee 5555 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) ccccttttiiiimmmmeeee(3C) syntax preceded by an at sign. For example ----TTTT ''''@@@@ MMMMoooonnnn MMMMaaaarrrr 4444 11113333::::00007777::::44447777 1111999999996666'''' ----OOOO _o_r_i_g_i_n By default samples are fetched from the start of the time window (see description of ----SSSS option) to the end of the time window (see description of ----TTTT option). The ----OOOO option allows the specification of an origin within the time window to be used as the initial sample time. This is useful for interactive use of a PCP tool with the ppppmmmmttttiiiimmmmeeee(1) VCR replay facility. The _o_r_i_g_i_n argument accepted by ----OOOO conforms to the same syntax and semantics as the _s_t_a_r_t_t_i_m_e argument for the ----TTTT option. For example ----OOOO ----0000 specifies that the initial position should be at the end of the time window; this is most useful when wishing to replay ``backwards'' within the time window. The _c_t_i_m_e argument for the ----OOOO, ----SSSS and ----TTTT options is based upon the calendar date and time format of ccccttttiiiimmmmeeee(3C), but may be a fully specified time string like MMMMoooonnnn MMMMaaaarrrr 4444 11113333::::00007777::::44447777 1111999999996666 or a partially specified time like MMMMaaaarrrr 4444 1111999999996666, MMMMaaaarrrr 4444, MMMMaaaarrrr, 11113333::::00007777::::55550000 or 11113333::::00008888. For any missing low order fields, the default value of 0 is assumed for hours, minutes and seconds, 1 for day of the month and Jan for months. Hence, the following are equivalent: ----SSSS ''''@@@@ MMMMaaaarrrr 1111999999996666'''' and ----SSSS ''''@@@@ MMMMaaaarrrr 1111 00000000::::00000000::::00000000 1111999999996666''''. If any high order fields are missing, they are filled in by starting with the year, month and day from the current time (real-time mode) or the time at the beginning of the PCP archive log (archive mode) and advancing the time until it matches the fields that are specified. So, for example if the time window starts by default at ``Mon Mar 4 13:07:47 1996'', then ----SSSS @@@@11113333::::11110000 corresponds to 13:10:00 on Mon Mar 4, 1996, while ----SSSS @@@@11110000::::00000000 corresponds to 10:00:00 on Tue Mar 5, 1996 (note this is the following day). For greater precision than afforded by ccccttttiiiimmmmeeee(3C), the seconds component may be a floating point number. Also the 12 hour clock (am/pm notation) is supported, so for example 11113333::::00007777 and 1111::::00007777 ppppmmmm are equivalent. PPPPEEEERRRRFFFFOOOORRRRMMMMAAAANNNNCCCCEEEE MMMMEEEETTTTRRRRIIIICCCCSSSS ---- NNNNAAAAMMMMEEEESSSS AAAANNNNDDDD IIIIDDDDEEEENNNNTTTTIIIIFFFFIIIIEEEERRRRSSSS The number of performance metric names supported by PCP in IRIX is of the order of a few thousand. There are fewer metrics on Linux, but still a considerable number. The PCP libraries and applications use an internal identification scheme that unambiguously associates a single integer with each known performance metric. This integer is known as the Performance Metric Identifier, or PMID. Although not a requirement, PMIDs tend to have global consistency across all systems, so a particular performance metric usually has the same PMID. PPPPaaaaggggeeee 6666 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) For all users and most applications, direct use of the PMIDs would be inappropriate (e.g. this would limit the range of accessible metrics, make the code hard to maintain, force the user interface to be particularly baroque, etc.). Hence a Performance Metrics Name Space (PMNS) is used to provide external names and a hierarchic classification for performance metrics. A PMNS is represented as a tree, with each node having a label, a pointer to either a PMID (for leaf nodes) or a set of descendent nodes in the PMNS (for non-leaf nodes). A node label must begin with an alphabetic character, followed by zero or more characters drawn from the alphabetics, the digits and character `_' (underscore). For alphabetic characters in a node label, upper and lower case are distinguished. By convention, the name of a performance metric is constructed by concatenation of the node labels on a path through the PMNS from the root node to a leaf node, with a ``.'' as a separator. The root node in the PMNS is unlabeled, so all names begin with the label associated with one of the descendent nodes below the root node of the PMNS, e.g. _k_e_r_n_e_l._p_e_r_c_p_u._s_y_s_c_a_l_l. Typically (although this is not a requirement) there would be at most one name for each PMID in a PMNS. For example _k_e_r_n_e_l._a_l_l._c_p_u._i_d_l_e and _d_i_s_k._d_e_v._r_e_a_d are the unique names for two distinct performance metrics, each with a unique PMID. Groups of related PMIDs may be named by naming a non-leaf node in the PMNS tree, e.g. _d_i_s_k. There may be PMIDs with no associated name in a PMNS; this is most likely to occur when specific PMIDs are not available in all systems, e.g. if ORACLE is not installed on a system, there is no good reason to pollute the PMNS with names for all of the ORACLE performance metrics. Note also that there is no requirement for the PMNS to be the same on all systems, however in practice most applications would be developed against a stable PMNS that was assumed to be a subset of the PMNS on all systems. Indeed the PCP distribution includes a default local PMNS for just this purpose. The default local PMNS is located at $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss////rrrrooooooootttt however the environment variable PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT may be set to the full pathname of a different PMNS which will then be used as the default local PMNS. Most applications do not use the local PMNS, but rather import parts of the PMNS as required from the same place that performance metrics are fetched, i.e. from ppppmmmmccccdddd(1) for live monitoring or from a PCP archive for retrospective monitoring. To explore the PMNS use ppppmmmmiiiinnnnffffoooo(1), or if the PCP product is installed the Metric Selection browser within ppppmmmmcccchhhhaaaarrrrtttt(1). PPPPaaaaggggeeee 7777 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPEEEERRRRFFFFOOOORRRRMMMMAAAANNNNCCCCEEEE MMMMEEEETTTTRRRRIIIICCCC SSSSPPPPEEEECCCCIIIIFFFFIIIICCCCAAAATTTTIIIIOOOONNNNSSSS In configuration files and (to a lesser extent) command line options, metric specifications adhere to the following syntax rules. If the source of performance metrics is real-time from ppppmmmmccccdddd(1) then the accepted syntax is _h_o_s_t::::_m_e_t_r_i_c[[[[_i_n_s_t_a_n_c_e_1,,,,_i_n_s_t_a_n_c_e_2,,,,...]]]] If the source of performance metrics is a PCP archive log then the accepted syntax is _a_r_c_h_i_v_e////_m_e_t_r_i_c[[[[_i_n_s_t_a_n_c_e_1,,,,_i_n_s_t_a_n_c_e_2,,,,...]]]] The _h_o_s_t::::, _a_r_c_h_i_v_e//// and [[[[_i_n_s_t_a_n_c_e_1,,,,_i_n_s_t_a_n_c_e_2,,,,...]]]] components are all optional. The ,,,, delimiter in the list of instance names may be replaced by white space. Special characters in _i_n_s_t_a_n_c_e names may be escaped by surrounding the name in double quotes or preceding the character with a backslash. White space is ignored everywhere except within a quoted _i_n_s_t_a_n_c_e name. An empty _i_n_s_t_a_n_c_e is silently ignored, and in particular ``[[[[]]]]'' is the same as no _i_n_s_t_a_n_c_e, while ``[[[[oooonnnneeee,,,,,,,,,,,,ttttwwwwoooo]]]]'' is parsed as specifying just the two instances ``oooonnnneeee'' and ``ttttwwwwoooo''. PPPPMMMMCCCCDDDD AAAANNNNDDDD AAAARRRRCCCCHHHHIIIIVVVVEEEE VVVVEEEERRRRSSSSIIIIOOOONNNNSSSS Since PCP version 2, version information has been associated with ppppmmmmccccdddd(1) and PCP archives. The version number is used in a number of ways, but most noticeably for the distributed ppppmmmmnnnnssss(4). In PCP version 1, the client applications would load the PMNS from the default PMNS file but in PCP version 2, the client applications extract the PMNS information from ppppmmmmccccdddd(1) or a PCP archive. Thus in PCP version 2, the version number is used to determine if the PMNS to use is from the default local file or from the actual current source of the metrics. EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT In addition to the PCP run-time environment and configuration variables described in the PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT section below, the following environment variables apply to all installations. PPPPCCCCPPPP____SSSSTTTTDDDDEEEERRRRRRRR Many PCP tools support the environment variable PPPPCCCCPPPP____SSSSTTTTDDDDEEEERRRRRRRR, which can be used to control where error messages are sent. When unset, the default behavior is that ``usage'' messages and option parsing errors are reported on standard error, other messages after initial startup are sent to the default destination for the tool, i.e. standard error for ASCII tools, or a dialog for GUI tools. PPPPaaaaggggeeee 8888 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) If PPPPCCCCPPPP____SSSSTTTTDDDDEEEERRRRRRRR is set to the literal value DDDDIIIISSSSPPPPLLLLAAAAYYYY then all messages will be displayed in a dialog. This is used for any tools launched from the IRIX Interactive Desktop (trademark) or from the PPPPeeeerrrrffffTTTToooooooollllssss icon catalog page. If PPPPCCCCPPPP____SSSSTTTTDDDDEEEERRRRRRRR is set to any other value, the value is assumed to be a filename, and all messages will be written there. PPPPCCCCPPPP____UUUUSSSSEEEE____SSSSTTTTDDDDEEEERRRRRRRR This environment variable, previously used by ppppmmmmllllaaaauuuunnnncccchhhh(5), ppppmmmmggggssssyyyyssss(1), ppppmmmmvvvviiiieeeewwww(1) and the ppppmmmmvvvviiiieeeewwww(1) front-end scripts (such as mmmmppppvvvviiiissss(1)), has been deprecated from the PCP 2.0 release onward and replaced by PPPPCCCCPPPP____SSSSTTTTDDDDEEEERRRRRRRR. PPPPMMMMCCCCDDDD____CCCCOOOONNNNNNNNEEEECCCCTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT When attempting to connect to a remote ppppmmmmccccdddd(1) on a machine that is booting, the connection attempt could potentially block for a long time until the remote machine finishes its initialization. Most PCP applications and some of the PCP library routines will abort and return an error if the connection has not been established after some specified interval has elapsed. The default interval is 5 seconds. This may be modified by setting PPPPMMMMCCCCDDDD____CCCCOOOONNNNNNNNEEEECCCCTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT in the environment to a real number of seconds for the desired timeout. This is most useful in cases where the remote host is at the end of a slow network, requiring longer latencies to establish the connection correctly. PPPPMMMMCCCCDDDD____RRRREEEECCCCOOOONNNNNNNNEEEECCCCTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT When a monitor or client application loses a connection to a ppppmmmmccccdddd(1), the connection may be re-established by calling a service routine in the PCP library. However, attempts to reconnect are controlled by a back-off strategy to avoid flooding the network with reconnection requests. By default, the back-off delays are 5, 10, 20, 40 and 80 seconds for consecutive reconnection requests from a client (the last delay will be repeated for any further attempts after the fifth). Setting the environment variable PPPPMMMMCCCCDDDD____RRRREEEECCCCOOOONNNNNNNNEEEECCCCTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT to a comma separated list of positive integers will re-define the back-off delays, e.g. setting PPPPMMMMCCCCDDDD____RRRREEEECCCCOOOONNNNNNNNEEEECCCCTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT to ``1,2'' will back-off for 1 second, then attempt another connection request every 2 seconds thereafter. PPPPMMMMCCCCDDDD____RRRREEEEQQQQUUUUEEEESSSSTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT For monitor or client applications connected to ppppmmmmccccdddd(1), there is a possibility of the application "hanging" on a request for performance metrics or metadata or help text. These delays may become severe if the system running ppppmmmmccccdddd crashes, or the network connection is lost. By setting the environment variable PPPPMMMMCCCCDDDD____RRRREEEEQQQQUUUUEEEESSSSTTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT to a real number of seconds, requests to ppppmmmmccccdddd will timeout after this number of seconds. The default behavior is to be willing to wait 10 seconds for a response from every ppppmmmmccccdddd for all applications. PPPPaaaaggggeeee 9999 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPMMMMCCCCDDDD____WWWWAAAAIIIITTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT When ppppmmmmccccdddd(1) is started from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp then the primary instance of ppppmmmmllllooooggggggggeeeerrrr(1) will be started if the configuration flag ppppmmmmllllooooggggggggeeeerrrr is chkconfig'ed on, some key applications from the _p_c_p._s_w._b_a_s_e subsystem are installed and ppppmmmmccccdddd is running and accepting connections. The check on ppppmmmmccccdddd's readiness will wait up to PPPPMMMMCCCCDDDD____WWWWAAAAIIIITTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT seconds. If ppppmmmmccccdddd has a long startup time (such as on a very large system), then PPPPMMMMCCCCDDDD____WWWWAAAAIIIITTTT____TTTTIIIIMMMMEEEEOOOOUUUUTTTT can be set to provide a maximum wait longer than the default 60 seconds. PPPPMMMMNNNNSSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTT If set, then interpreted as the the full pathname to be used as the default local PMNS for ppppmmmmLLLLooooaaaaddddNNNNaaaammmmeeeeSSSSppppaaaacccceeee(3). Otherwise, the default local PMNS is located at $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppccccpppp////ppppmmmmnnnnssss////rrrrooooooootttt for base PCP installations. PPPPCCCCPPPP____CCCCOOOOUUUUNNNNTTTTEEEERRRR____WWWWRRRRAAAAPPPP Many of the performance metrics exported from PCP agents have the semantics of _c_o_u_n_t_e_r meaning they are expected to be monotonically increasing. Under some circumstances, one value of these metrics may smaller than the previously fetched value. This can happen when a counter of finite precision overflows, or when the PCP agent has been reset or restarted, or when the PCP agent is exporting values from some underlying instrumentation that is subject to some asynchronous discontinuity. The environment variable PPPPCCCCPPPP____CCCCOOOOUUUUNNNNTTTTEEEERRRR____WWWWRRRRAAAAPPPP may be set to indicate that all such cases of a decreasing ``counter'' should be treated as a counter overflow, and hence the values are assumed to have wrapped once in the interval between consecutive samples. This ``wrapping'' behavior was the default in earlier PCP versions, but by default has been disabled in PCP release from version 1.3 on. PPPPCCCCPPPP____LLLLIIIICCCCEEEENNNNCCCCEEEE____NNNNOOOOWWWWAAAARRRRNNNNIIIINNNNGGGG or PPPPCCCCPPPP____LLLLIIIICCCCEEEENNNNSSSSEEEE____NNNNOOOOWWWWAAAARRRRNNNNIIIINNNNGGGG Many of the PCP client programs require that a valid software license be present on the host on which the client is running (the license is node-locked). In the case that such a valid license is present, but is due to expire within the next 30 days, a message or popup notifier appears informing the user of this condition. These warnings can be disabled by setting PPPPCCCCPPPP____LLLLIIIICCCCEEEENNNNCCCCEEEE____NNNNOOOOWWWWAAAARRRRNNNNIIIINNNNGGGG or PPPPCCCCPPPP____LLLLIIIICCCCEEEENNNNSSSSEEEE____NNNNOOOOWWWWAAAARRRRNNNNIIIINNNNGGGG in the environment. PPPPMMMMDDDDAAAA____PPPPAAAATTTTHHHH The PPPPMMMMDDDDAAAA____PPPPAAAATTTTHHHH environment variable may be used to modify the search path used by ppppmmmmccccdddd(1) and ppppmmmmNNNNeeeewwwwCCCCoooonnnntttteeeexxxxtttt(3) (for PPPPMMMM____CCCCOOOONNNNTTTTEEEEXXXXTTTT____LLLLOOOOCCCCAAAALLLL contexts) when searching for a daemon or DSO PMDA. The syntax follows that for PPPPAAAATTTTHHHH in sssshhhh(1), i.e. a colon separated list of directories, and the default search path is ``/var/pcp/lib:/usr/pcp/lib''. PPPPaaaaggggeeee 11110000 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPMMMMCCCCDDDD____PPPPOOOORRRRTTTT The TPC/IP port used by ppppmmmmccccdddd(1) to create the socket for incoming connections and requests, is by default port number 4321. This may be over-ridden by setting PPPPMMMMCCCCDDDD____PPPPOOOORRRRTTTT to a different port number. If a non-default port is used when ppppmmmmccccdddd(1) is started, then every monitoring application connecting to that ppppmmmmccccdddd(1) must also have PPPPMMMMCCCCDDDD____PPPPOOOORRRRTTTT set in their environment before attempting a connection. The following environment variables are relevant to installations in which ppppmmmmllllooooggggggggeeeerrrr(1), the PCP archive logger, is used. PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR____PPPPOOOORRRRTTTT The environment variable PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR____PPPPOOOORRRRTTTT may be used to change the base TCP/IP port number used by ppppmmmmllllooooggggggggeeeerrrr(1) to create the socket to which ppppmmmmllllcccc(1) instances will try and connect. The default base port number is 4330. When used, PPPPMMMMLLLLOOOOGGGGGGGGEEEERRRR____PPPPOOOORRRRTTTT should be set in the environment before ppppmmmmllllooooggggggggeeeerrrr(1) is executed. If you have the PCP product installed, then the following environment variables are relevant to the Performance Metrics Domain Agents (PMDAs). PPPPMMMMDDDDAAAA____LLLLOOOOCCCCAAAALLLL____PPPPRRRROOOOCCCC If set, then a context established with the _t_y_p_e of PPPPMMMM____CCCCOOOONNNNTTTTEEEEXXXXTTTT____LLLLOOOOCCCCAAAALLLL will have access to the ``proc'' PMDA to retrieve performance metrics about individual processes. PPPPMMMMDDDDAAAA____LLLLOOOOCCCCAAAALLLL____SSSSAAAAMMMMPPPPLLLLEEEE If set, then a context established with the _t_y_p_e of PPPPMMMM____CCCCOOOONNNNTTTTEEEEXXXXTTTT____LLLLOOOOCCCCAAAALLLL will have access to the ``sample'' PMDA if this optional PMDA has been installed locally. PPPPMMMMIIIIEEEECCCCOOOONNNNFFFF____PPPPAAAATTTTHHHH If set, ppppmmmmiiiieeeeccccoooonnnnffff(1) will form its ppppccccoooonnnnffff(5) specification (set of parameterized ppppmmmmiiiieeee(1) rules) using all valid ppppccccoooonnnnffff files found below each subdirectory in this colon-separated list of subdirectories. If not set, the default is ////vvvvaaaarrrr////ppppccccpppp////ppppccccoooonnnnffff. FFFFIIIILLLLEEEESSSS ////eeeettttcccc////ppppccccpppp....ccccoooonnnnffff Configuration file for the PCP runtime environment, see ppppccccpppp....ccccoooonnnnffff(4). $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp Script for starting and stopping ppppmmmmccccdddd(1). $$$$PPPPCCCCPPPP____PPPPMMMMCCCCDDDDCCCCOOOONNNNFFFF____PPPPAAAATTTTHHHH Control file for ppppmmmmccccdddd(1). $$$$PPPPCCCCPPPP____PPPPMMMMCCCCDDDDOOOOPPPPTTTTIIIIOOOONNNNSSSS____PPPPAAAATTTTHHHH Command line options passed to ppppmmmmccccdddd(1) when it is started from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp. All the command line option lines should start with a hyphen as the first character. This file can also contain environment variable settings of the form "VARIABLE=value". PPPPaaaaggggeeee 11111111 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) $$$$PPPPCCCCPPPP____BBBBIIIINNNNAAAADDDDMMMM____DDDDIIIIRRRR Location of PCP utilities for collecting and maintaining PCP archives, PMDA help text, PMNS files etc. $$$$PPPPCCCCPPPP____PPPPMMMMDDDDAAAASSSS____DDDDIIIIRRRR Parent directory of the installation directory for Dynamic Shared Object (DSO) PMDAs. $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////ppppmmmmccccdddd Default location of log files for ppppmmmmccccdddd(1), current directory for running PMDAs. Archives generated by ppppmmmmllllooooggggggggeeeerrrr(1) are generally below $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////ppppmmmmllllooooggggggggeeeerrrr. $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////ppppmmmmccccdddd////ppppmmmmccccdddd....lllloooogggg Diagnostic and status log for the current running ppppmmmmccccdddd(1) process. The first place to look when there are problems associated with ppppmmmmccccdddd. $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////ppppmmmmccccdddd////ppppmmmmccccdddd....lllloooogggg....pppprrrreeeevvvv Diagnostic and status log for the previous ppppmmmmccccdddd(1) instance. $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////NNNNOOOOTTTTIIIICCCCEEEESSSS Log of ppppmmmmccccdddd(1) and PMDA starts, stops, additions and removals. $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg Contains directories of configuration files for several PCP tools. $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmccccdddd////rrrrcccc....llllooooccccaaaallll Local script for controlling PCP boot, shutdown and restart actions. $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss Directory containing the set of PMNS files for all installed PMDAs. $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss////rrrrooooooootttt The ASCII PPPPMMMMNNNNSSSS(4) exported by ppppmmmmccccdddd(1) by default. This PMNS is be the super set of all other PMNS files installed in $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ppppmmmmnnnnssss. In addition, if the PCP product is installed the following files and directories are relevant. $$$$PPPPCCCCPPPP____LLLLOOOOGGGG____DDDDIIIIRRRR////NNNNOOOOTTTTIIIICCCCEEEESSSS In addition to the ppppmmmmccccdddd(1) and PMDA activity, may be used to log alarms and notices from ppppmmmmiiiieeee(1) via ppppmmmmppppoooosssstttt(1). $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnttttrrrroooollll Control file for ppppmmmmllllooooggggggggeeeerrrr(1) instances launched from $$$$PPPPCCCCPPPP____RRRRCCCC____DDDDIIIIRRRR////ppppccccpppp and/or managed by ppppmmmmllllooooggggggggeeeerrrr____cccchhhheeeecccckkkk(1) and ppppmmmmllllooooggggggggeeeerrrr____ddddaaaaiiiillllyyyy(1) as part of a production PCP archive collection setup. $$$$PPPPCCCCPPPP____VVVVAAAARRRR____DDDDIIIIRRRR////ccccoooonnnnffffiiiigggg////ppppmmmmssssnnnnaaaapppp////ccccoooonnnnttttrrrroooollll Control file for ppppmmmmssssnnnnaaaapppp(1) to produce GIF images of recent performance as displayed by ppppmmmmcccchhhhaaaarrrrtttt(1) from PCP archives. $$$$PPPPCCCCPPPP____DDDDEEEEMMMMOOOOSSSS____DDDDIIIIRRRR Contains examples for using a variety of PCP tools and the PCP online tutorial. PPPPCCCCPPPP EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT Environment variables with the prefix PPPPCCCCPPPP____ are used to parameterize the file and directory names used by PCP. On each installation, the file ////eeeettttcccc////ppppccccpppp....ccccoooonnnnffff contains the local values for these variables. The $$$$PPPPCCCCPPPP____CCCCOOOONNNNFFFF variable may be used to specify an alternative configuration PPPPaaaaggggeeee 11112222 PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) PPPPCCCCPPPPIIIINNNNTTTTRRRROOOO((((1111)))) file, as described in ppppccccpppp....ccccoooonnnnffff(4). SSSSEEEEEEEE AAAALLLLSSSSOOOO oooovvvviiiieeeewwww(1), ppppmmmmccccdddd(1), ppppmmmmeeeemmmm(1), ppppmmmmiiiieeee(1), ppppmmmmiiiinnnnffffoooo(1), ppppmmmmkkkkssssttttaaaatttt(1), ppppmmmmllllooooggggggggeeeerrrr(1), ppppmmmmvvvvaaaallll(1), ppppccccpppp....ccccoooonnnnffff(4), ppppccccpppp....eeeennnnvvvv(4), ppppmmmmnnnnssss(4) and ppppmmmmllllaaaauuuunnnncccchhhh(5). If the Performance Co-Pilot product is installed, then the following entries are also relevant: ppppmmmmllllooooggggggggeeeerrrr____ddddaaaaiiiillllyyyy(1), ddddkkkkvvvviiiissss(1), mmmmppppvvvviiiissss(1), nnnnffffssssvvvviiiissss(1), oooossssvvvviiiissss(1), ppppccccpppp(1), ppppmmmmcccchhhhaaaarrrrtttt(1), ppppmmmmdddduuuummmmpppptttteeeexxxxtttt(1), ppppmmmmggggeeeevvvvccccttttrrrr(1) and ppppmmmmggggssssyyyyssss(1). Also refer to the Insight books _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _U_s_e_r'_s _a_n_d _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e and _P_e_r_f_o_r_m_a_n_c_e _C_o-_P_i_l_o_t _P_r_o_g_r_a_m_m_e_r'_s _G_u_i_d_e. If you have the PCP product, relevant information is also available from the on-line PCP Tutorial. Provided the ppppccccpppp....mmmmaaaannnn....ttttuuuuttttoooorrrriiiiaaaallll subsystem from the PCP images has been installed, access the URL ffffiiiilllleeee::::$$$$PPPPCCCCPPPP____DDDDOOOOCCCC____DDDDIIIIRRRR////TTTTuuuuttttoooorrrriiiiaaaallll////iiiinnnnddddeeeexxxx....hhhhttttmmmmllll from your web browser. PPPPaaaaggggeeee 11113333 
