[ Previous |
Next |
Contents |
Glossary |
Home |
Search ]
AIX Version 4.3 System Management Guide: Operating System and Devices
Restarting the runacct Command
Prerequisites
- You must have the accounting system
installed.
- You must have root user or adm group authority.
Note: The
runacct
command can fail for a variety of reasons, most commonly because the system
goes down, the /usr file system runs out of space, or the
/var/adm/wtmp file has records with inconsistent date stamps.
Procedure
If the runacct command is
unsuccessful, do the following:
- Check the /var/adm/acct/nite/active
mmdd file for error messages.
- If both the active file and lock files exist in
acct/nite, check the accterr file, where error messages are redirected when the
cron daemon calls
the runacct command.
- Perform any actions needed to eliminate
errors.
- Restart the runacct command.
- To restart the runacct command for a
specific date, enter the following:
nohup runacct 0601 2>> \
/var/adm/acct/nite/accterr &
This restarts the runacct program for June 1 (0601
).
The runacct program reads the /var/adm/acct/nite/statefile file
to find out with which state to begin. All standard error output is appended
to the /var/adm/acct/nite/accterr file.
- To restart the runacct program at a
specified state, for example, the MERGE state, enter the following:
nohup runacct 0601 MERGE 2>> \
/var/adm/acct/nite/accterr &
[ Previous |
Next |
Contents |
Glossary |
Home |
Search ]