csa(1M)csa(1M)NAMEcsa - overview of Comprehensive System Accounting (CSA)
DESCRIPTION
The IRIX operating system supports three accounting packages: standard
UNIX System V accounting, IRIX extended accounting, and IRIX
Comprehensive System Accounting (CSA). CSA is a set of C programs and
shell scripts that, like the other accounting packages, provide methods
for collecting per-process resource usage data, monitoring disk usage,
and charging fees to specific login accounts.
CSA provides the following features which are not available with the
other accounting packages:
o Per-job accounting
o Daemon accounting (tape, NQS, and workload management systems)
o Flexible accounting periods (daily and periodic accounting reports
can be generated as often as desired and not restricted to once per
day or once per month)
o Flexible system billing units (SBUs)
o Offline archiving of accounting data
o User exits for site specific customization of daily and periodic
accounting
o Configurable parameters within the /etc/csa.conf file
o User job accounting (ja(1) command)
CSA takes this per-process accounting information and combines it by job
identifier (jid) within system boot uptime periods. CSA accounting for
an interactive job consists of all accounting data for a given job
identifier during a single system boot period. CSA accounting for a
batch job includes the accounting data associated with the batch system
identifier, which may consist of one or more job identifiers and may span
multiple reboots.
Daemon accounting records are written at the completion of daemon
specific events. These records are combined with per-process accounting
records associated with the same interactive or batch job.
By default, CSA only reports accounting data for terminated jobs.
Interactive jobs, cron jobs and at jobs terminate when the last process
in the job exits, which is normally the login shell. An NQS or workload
management job is recognized as terminated by CSA based upon daemon
accounting records and an end-of-job record for that job. Jobs which are
still active are recycled into the next accounting period. This behavior
can be changed through use of the csarun -A option.
Page 1
csa(1M)csa(1M)
A system billing unit (SBU) is a unit of measure that reflects use of
machine resources. SBUs are defined in the CSA configuration file
/etc/csa.conf and are set to 0.0 by default. The weighting factor
associated with each field in the CSA accounting records can be altered
to obtain an SBU value suitable for your site. See the IRIX Admin:
Resource Administration manual for further information.
The CSA accounting records are not written into the System V pacct file
but are written into a separate CSA /var/adm/acct/day/pacct file. The
CSA commands can only be used with CSA generated accounting records.
Similarly, the System V accounting commands can only be used with System
V generated accounting records.
There are four user exits available with the csarun(1M) daily accounting
script. There is one user exit available with the csaperiod(1M) periodic
accounting script. These user exits allow sites to tailor the daily and
periodic run of accounting to their specific needs by creating user exit
scripts to perform any additional processing and to allow for archiving
of accounting data. See the csarun(1M) and csaperiod(1M) man pages for
further information.
CSA provides two user accounting commands, csacom(1) and ja(1). The
csacom command reads the CSA pacct file and writes selected accounting
records to standard output. The csacom command is very similar to the
System V acctcom(1) command. The ja command provides job accounting
information for the current job of the caller. This information is
obtained from a separate user job accounting file to which the kernel
writes. See the csacom(1) and ja(1) man pages for further information.
The /etc/csa.conf file contains CSA configuration variables. These
variables are used by the CSA commands.
Like any accounting or monitoring package, the CSA features do contribute
to overall system overhead. For this reason, CSA is disabled in the
kernel by default. To enable CSA, use the systune(1M) program to modify
the following variable:
do_csaacct Enables CSA job accounting if non-zero
The csaswitch command is used to dynamically configure on or off CSA
record types, set memory and I/O threshold values, switch the CSA pacct
file, and provide status information. See the csaswitch(1M) man page for
further information.
CSA can be automatically configured on across system reboots using the
chkconfig csaacct on command.
INSTALLATION/STARTUP SUMMARY
The following steps are required to set up CSA job accounting:
Page 2
csa(1M)csa(1M)
o Enable CSA within the kernel by using the systune utility to set
do_csaacct to a non-zero value
o Use the inst(1M) utility to install the eoe.sw.csaacct subsystem from
your IRIX distribution media. Installing CSA also requires the
eoe.sw.acct and eoe.sw.jlimits subsystems to be installed. It will
be necessary to reboot the system after completing this step.
o Configure CSA on across system reboots by using the chkconfig utility
as follows:
chkconfig csaacct on
o Modify the CSA configuration variables in /etc/csa.conf as desired
o Use csaswitch to configure on the accounting record types and
thresholds defined in /etc/csa.conf as follows:
csaswitch -c on
This step will be done automatically for subsequent system reboots when
CSA is configured on via the chkconfig(1M) utility.
FILES
/usr/lib/acct Contains the CSA administrator commands
/usr/bin Contains the CSA user commands, csacom
and ja
/etc/csa.conf CSA configuration file
/var/adm/acct/day/pacct Current process accounting file
/var/adm/acct/sum/csa CSA daily reports and data files
/var/adm/acct/fiscal/csa CSA periodic reports and data files
SEE ALSOacctdisk(1M), chargefee(1M), csaaddc(1M), csabuild(1M), csachargefee(1M),
csackpacct(1M), csacms(1M), csacom(1), csacon(1M), csacrep(1M),
csadrep(1M), csaedit(1M), csagetconfig(1M), csajrep(1M), csaperiod(1M),
csarecy(1M), csarun(1M), csaswitch(1M), csaverify(1M), dodisk(1M), ja(1),
lastlogin(1M).
IRIX Admin: Resource Administration
Page 3
