LNEXT
ONELCLEAN
UTERMINAL
TERMINAL
NEXT
$V1$
HILINE
PAUSE
ACCTREE
/usr
|
/lib
|
/acct
|
-------------------------------------
| | | |
| | | |
/nite /sum /fiscal prdaily
PRCRON
0 3 * * 0-6 /bin/su - adm -c /usr/lib/acct/runnact
0 2 * * 0-6 /bin/su - adm -c /usr/bin/acct/chargefee user 5
30 1 * * 3 /usr/bin/acct/dodisk
10 * * * * /bin/su - adm -c /usr/lib/acct/ckpacct
30 4 1 * * /bin/su - adm -c /usr/lib/acct/monacct
GO
Because the accounting utilities do use considerable system
resources, both CPU time and disk space, it is important
that these utilities be executed only when necessary.
First of all, the accounting system needs to be running only when
your UNIX system is in a multi-user mode. You can accomplish
this by inserting the line:
/bin/su - adm -c /usr/lib/acct/startup
into your /etc/rc file!
Secondly, different utilities need to be run at different intervals.
The intervals at which these utilities can be run may be specified,
as you may recall, in the /usr/lib/crontab file, which is read
every minute by the cron daemon.
The daily accounting shell procedure runnact processes
connect time, fee, disk, and process accounting files. It also
prepares daily and cumulative summary files for use by prdaily
or for billing purposes (see your Administrator Guide for details).
This procedure should be run at non-prime time, for example, at 3 a.m.
daily, which would result in a crontab entry as shown above.
0 3 * * 0-6 /bin/su - adm -c /usr/lib/acct/runnact
The chargefee (if any) program can be used to bill users
for connect time, disk usage, file restores, etc.
It adds records to the /usr/adm/fee file
which are picked up and processed by the next execution of
runnact and merged into the total accounting records.
Let us assume that this procedure runs at 2:00 a.m. daily to produce
new fee reports for runnact; therefore, the crontab
entry for this command would be as shown above.
0 2 * * 0-6 /bin/su - adm -c /usr/bin/acct/chargefee user 5
The dodisk program produces disk usage summary files
that are later merged with the cumulative summary files by
runnact. Assuming that disk usage is progressing slowly, it
would then be sufficient to run this program on a weekly basis,
again during nonprime time, e.g., at 1:30 a.m. on Tuesday (3rd day
of the week). The crontab entry for this would be as shown above.
30 1 * * 3 /usr/bin/acct/dodisk
Because the size of the report files grows with accounting system
operation, there is a need for a program to control the size of
these files, especially the size of /usr/adm/pacct. The
program that does just that is ckpacct. This program should
be run probably every 10 minutes during system operation, which
would result in a crontab entry as shown above.
10 * * * * /bin/su - adm -c /usr/lib/acct/ckpacct
Furthermore, the program monacct produces monthly accounting
reports, so naturally it should be run monthly. A logical
day would be the 1st day of the month, at 4:30 a.m., which would
result in a crontab entry as shown above!
30 4 1 * * /bin/su - adm -c /usr/lib/acct/monacct
There are other important accounting programs; however, it
is hoped that at this point you, - the resourceful system
administrator, will be able to obtain additional information
from the System Administrator Guide and the System Administrator
Reference Manual!
Let us verify the content of the
/usr/lib/crontab file on your
system:
$PROMPT$
That is correct!
You've got it on the 2nd try.
Good, you understand the concept.
Please type cat /usr/lib/crontab
Please type cat /usr/lib/crontab
You will be helped this time!
$PROMPT$
FORGET1
cat /usr/lib/crontab
Please observe partial content
of the crontab file above.