HP-UX Reference (11i v2 07/12) - 1 User Commands A-M (vol 1)
c
caliper(1)
For Integrity Systems Only
caliper(1)
Caliper 4.3 Caliper 4.3
(Requires Optional HP Caliper Software)
Process Selection
When dealing with multi-process applications, it is important to be able to select processes to be measured
in a process tree. This section explains how to do this selection by using the
--process option.
Caliper has a choice between three behaviors when considering what to do with a process:
measure The process is measured. Caliper is informed of new processes generated via
fork,
vfork,orexec.
track The process is not measured. Caliper is informed of new processes generated via
fork,
vfork,orexec.
ignore The process is not measured. Caliper is not informed of new processes generated via
fork, vfork,orexec.
Caliper will pick which behavior is chosen depending on the
process option. See PLATFORM-SPECIFIC
ADDENDA below for additional information on process selection.
This section uses the term root process. The root process is the process at the root of the process tree. It
is either the process started by Caliper or the process to which Caliper attaches.
The simple options are:
--process=root
Only the root process is measured.
--process=root-forks
Only the root process and processes forked from the root process are measured.
--process=all
Every process in the process tree is measured. This is the default for all measurements.
--process=default
This option is available to be able to explicitly request the default behavior. This is equivalent to speci-
fying root for all measurements.
The complex options are:
--process= [some:][OPT1,...]PATTERN
Each --process=some:
... argument provided to Caliper is interpreted as an additional filter.
Those filters are applied in order to each new process. If a filter matches the process, the behavior
(
measure, track, ignore) associated with the process is memorized. Caliper will use the
behavior of the last matching filter to determine what to do with the process.
When no OPT1,... component is provided, the default interpretation is as follows: the PATTERN com-
ponent is interpreted as a list of
glob patterns separated by colons (:); if the basename of the execut-
able matches any of those patterns, the process is measured, otherwise it is tracked.
The presence of keywords in OPT1
,... modifies those semantics as follow:
measure Processes matching this filter will be measured.
track Processes matching this filter will be tracked.
ignore Processes matching this filter will be ignored.
glob The PATTERN is interpreted as a list of colon-separated glob patterns.
regexp The PATTERN is interpreted as a Python/Perl regular expression that is tested using
the search() function (i.e., any non-empty match will be considered a positive
match).
file The string used against the PATTERN is the basename of the main executable of the
process.
arg0argv0 The string used against the PATTERN is argument 0 of the process.
arg1argv1 The string used against the PATTERN is argument 1 of the process.
root The filter only matches the root process.
fork The filter only matches processes created via fork().
exec The filter only matches processes created by exec().
104 Hewlett-Packard Company − 14 − HP-UX 11i Version 2: December 2007 Update