wlmaudit(1M)wlmaudit(1M)NAMEwlmaudit - display audit data generated by the HP-UX Workload Manager
(WLM) and the WLM global arbiter
SYNOPSIS
[-d {wlmd | wlmpard}] [-s start_date] [-e end_date] [-o html]
DESCRIPTION
displays the audit data that is generated when you use the option with
the WLM daemon or with the WLM global arbiter daemon
OPTIONS
Displays usage information and exits.
This option overrides all other options.
Displays version information and exits. This option overrides all
options
other than
Specifies the daemon for which to display audit data. If you do not
specify
this option, displays the audit data from both daemons, if avail‐
able.
Instructs
to display audit data beginning from start_date, inclusive. The
default is 01/01/1900. Use the format mm/dd/yyyy when specifying
start_date.
Instructs
to display audit data up to end_date, inclusive. The default is
the date on the current system. Use the format mm/dd/yyyy when
specifying end_date.
Displays audit data in a formatted HTML report. The default is text.
STRUCTURE OF AUDIT FILES
takes the comma-separated data from audit files and displays it in an
easily readable report. However, if you would like to use these files
directly, they are located in the directory /var/opt/wlm/audit/, as
described in the FILES section. Here is an example entry from one of
these files:
host1, 10/10/2002, group1, PRM, 10.000000, 0.000417, 0.000153
Each line has seven fields:
Field 1 The name of the host from which the data was gathered
Field 2 The date (mm/dd/yyyy) the data was gathered
Field 3 The name of the entity on which the data is focused
Field 4 The type of entity. Possible types are:
NPAR - an nPartition
PRM - a PRM group (also known as a workload group)
VPAR - a virtual partition
Field 5 Approximate number of hours of data available for the
entity
Field 6 The CPU entitlement, or allocation, for the entity for
the date shown (in CPU hours)
In passive mode, the entry is this field is always 0.0.
Field 7 The CPU usage for the entity for the date shown (in CPU
hours)
NOTES
In order to ensure the smooth running of the operating system and key
HP-UX daemons, WLM runs these system processes in a special workload
group called PRM_SYS. This group is not restrained by WLM: It consumes
system resources as needed. As a result, a workload group's CPU usage
may be less than its allocation because PRM_SYS requires some of the
group's resources. However, the low usage could also be the result of
the group's low CPU demands, or a combination of the two factors.
Also, CPU usage might at times be slightly above the allocation due to
dynamics in the CPU scheduler that WLM uses. Likewise, if memory man‐
agement is enabled, a workload's memory usage may be less than the num‐
ber of memory shares for reasons similar to those just stated. It could
also be slightly above the memory shares value due to extreme paging
pressure or when the current group allocation is being reduced.
RETURN VALUE
returns exit status if no errors occur, or nonzero if there are errors.
DEPENDENCIES
requires /opt/perl/bin/perl.
generates its reports from files created by the and daemons. You must
use the option with these daemons to create these files before using
Also, be sure to set in your WLM configuration and in your WLM global
arbiter configuration, if applicable, as indicated in the wlmconf(4)
and wlmparconf(4) manpages.
AUTHOR
was developed by HP.
FEEDBACK
If you would like to comment on the current HP-UX WLM functionality or
make suggestions for future releases, please send email to:
wlmfeedback@rsn.hp.com
FILES
Comma-separated audit data generated by
for the month and year designated by monyyyy. For example,
wlmd.jun2003.
Comma-separated audit data generated by
for the month and year designated by monyyyy. For example, wlm‐
pard.jun2003.
SEE ALSOwlmd(1M), wlmpard(1M), wlm(5)
HP-UX Workload Manager User's Guide (/opt/wlm/share/doc/WLMug.pdf)
HP-UX Workload Manager homepage (http://www.hp.com/go/wlm)
wlmaudit(1M)
