Audit.handler.file.size; Audit.handler.file.name - Dell PowerVault ML6000 User Manual

Usage
This parameter is used to indicate into which directory the audit record files
should be written. Note that if the directory does not exist, the Encryption Key
Manager will attempt to create the directory. If not successful, however, the
Encryption Key Manager will not start. It is recommended that the directory exist
prior to running the Encryption Key Manager. Note also that the User ID under
which the Encryption Key Manager runs must have write access to the directory
specified.
Examples
To set the directory to /var/ekm/ekm1/audit:
Audit.handler.file.directory=/var/ekm/ekm1/audit

Audit.handler.file.size

Syntax
Audit.handler.file.size=sizeInKiloBytes
Usage
This parameter is used to indicate the size limit upon which an audit file is closed
and a new audit file is then written to. Note that the actual size of the resulting
audit file may exceed this value by several bytes as the file is closed after the size
limit has been exceeded.
Examples
To set the maximum file size to roughly 2 megabytes, enter:
Audit.handler.file.size=2000

Audit.handler.file.name

Syntax
Audit.handler.file.name=fileName
Usage
Use this parameter to specify the base file name, within the specified audit
directory to use as the base name in creating audit log files. Note that this
parameter must contain only the base file name and not the fully qualified path
name. The full name of the audit log file will have the value corresponding to the
time upon which the file was written appended to this name.
To show this, consider an example where the Audit.handler.file.name value is set
to ekm.log. The full name of the file(s) will be something like: ekm.log.2315003554.
The appended string can be used to help determine the order in which the audit
log files were created – higher number values indicate newer audit log files.
Examples
An example setting the base name to ekm.log is:
Audit.handler.file.name=ekm.log
7-3
Chapter 7. Audit Records