UsageThis parameter is used to indicate into which directory the audit record filesshould be written. Note that if the directory does not exist, the Encryption KeyManager will attempt to create the directory. If not successful, however, theEncryption Key Manager will not start. It is recommended that the directory existprior to running the Encryption Key Manager. Note also that the User ID underwhich the Encryption Key Manager runs must have write access to the directoryspecified.ExamplesTo set the directory to /var/ekm/ekm1/audit:Audit.handler.file.directory=/var/ekm/ekm1/auditAudit.handler.file.sizeSyntaxAudit.handler.file.size=sizeInKiloBytesUsageThis parameter is used to indicate the size limit upon which an audit file is closedand a new audit file is then written to. Note that the actual size of the resultingaudit file may exceed this value by several bytes as the file is closed after the sizelimit has been exceeded.ExamplesTo set the maximum file size to roughly 2 megabytes, enter:Audit.handler.file.size=2000Audit.handler.file.nameSyntaxAudit.handler.file.name=fileNameUsageUse this parameter to specify the base file name, within the specified auditdirectory to use as the base name in creating audit log files. Note that thisparameter must contain only the base file name and not the fully qualified pathname. The full name of the audit log file will have the value corresponding to thetime upon which the file was written appended to this name.To show this, consider an example where the Audit.handler.file.name value is setto 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 auditlog files were created – higher number values indicate newer audit log files.ExamplesAn example setting the base name to ekm.log is:Audit.handler.file.name=ekm.logChapter 7. Audit Records 7-3
