Technical article 103340

What are the basics for using auditing in SCO UNIX or Open Desktop?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

What are the basics for setting up and using auditing?

Solution

First read the chapter on auditing in your System Administrator's Guide. The following is meant to highlight commonly asked questions about auditing.

Auditing uses a lot of disk space and affects system performance. For example, upon system startup it could take up to 3 minutes longer to get the first login prompt.

Select events to be audited.  For best results, select all users
to be audited.
Enable auditing.  Once auditing is enabled, do not change the
events or users or other parameters to be audited.

Auditing sessions can be viewed by using the Sysadmsh. Select Audit->Files->List.

Each auditing session represents the time between system shutdowns, or when auditing was disabled, and then re-enabled.

The stop time is not reported accurately and this will be corrected in the next release.

To specify different directories, for where the audit files will be stored, use the Sysadmsh:

Select Audit->Collection-> Directories->Create or Add
          You can change where the next sessions audit files will be stored
	  any time.  You do not need to disable auditing.  With the next system
	  startup, the audit files will be in the newly specified directory.

Backups can be done by either using Sysadmsh:

Select Audit->Files->Backup

or auditing files can be backed up as part of general backups.

Once a session is backed up, the associated files should be removed:

Select Audit->Files->Delete
Restoration of auditing files is not done by audit session,
but by the media selected.  All auditing sessions on a given
media will be restored.  However, files with an older date
will not overwrite the same files with a newer or same date.
The following message indicates the auditing parameters have
been reset and the session numbers are starting over.  Upon
system startup previous auditing files are overwritten:
Warning: Overwriting exising audit collection file
/tcb/audittmp/<audit1>/CFxxx

Audit->Collection->Reset will reset all auditing parameters back to the system defaults, including directories (returned to audit1 and audit2 only), events, ids, and parameters.

To start session numbers over at the number 1, delete all sessions and reset parameters.

Audit Files
-----------
For example, if there are two auditing sessions, the following
files will exist:
in /tcb/files/audit
CAFLOG.00001          master log files
CAFLOG.00002
in /tcb/audittmp/audit1    <or any other specified directory>
CAF00001.00000        collection files
CAF00002.00000
CF00001.000xx         there could be many of these
CF00002.000xx         files for each session
CF00002.000xx

To disable and re-enable auditing manually, without shutting down in order to start a new session, do the following:

To stop auditing:
/tcb/bin/auditcmd -d
To start auditing:
/tcb/bin/auditcmd -e
/tcb/bin/auditd
/tcb/bin/auditcmd -m

See also

auditcmd(ADM); auditd(ADM)

From the Xinuos technical article database, record 103340. Reproduced with permission. The original is at www.sco.com/ta/103340, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.