How do you manage the contents of the PSF DSS accounting data file?
An installation with a regular schedule of printing jobs will accumulate accounting and audit data that must be managed carefully to avoid potential performance problems. Periodically, the log files must be either purged or moved to a different directory. If you do not do either of these tasks, your installation will run out of space on the file system, preventing you from printing any more jobs. To avoid this problem, you should purge or move the accounting and audit logs as part of your system maintenance.
To retain a record of PSF DSS accounting and audit data, you need to move the existing log files to a new directory. Use this procedure:
- Go to the directory where the log file, for example, podaccount.log, is located by specifying:
- Move the podaccount.log file to a directory named 1quarter96 by specifying:
mv podaccount.log /1quarter96This command moves the existing file to the new directory and removes it from the /var/psf directory. The next time a job is submitted for printing from InfoPrint Submit, InfoPrint will create a new podaccount.log file in the /var/psf directory and write a single line of data for each job.
We recommend you move the data to another file system rather than deleting it from the system. This lets you store accounting data and delete it from the system when you no longer need to refer to it. If you want to delete the podaccount.log file without storing the data in another directory,
cd /var/psfThis command moves you into the correct path.
rm podaccount.logWhen the command-line prompt returns, you know that the podaccount.log file has been deleted from the system.
lsThis command displays the contents of your directory for you to verify that the file has been deleted. When the next job is submitted for printing, InfoPrint creates a new podaccount.log file and writes the data into that file.