Audit.handler.file.multithreadsSyntaxAudit.handler.file.multithreads={yes|true|no|false}UsageIf specified as true, then a separate thread is used to write the event data to theaudit log, allowing the current thread of execution (operation) to continue withoutwaiting for the write to the audit log to complete. Use of multiple threads is thedefault behavior.ExamplesAn example setting the base name to true is:Audit.handler.file.multithreads=trueAudit.handler.file.threadlifespanSyntaxAudit.handler.file.threadlifespan=timeInSecondsUsageThis parameter is used to specify the maximum time a thread should be expectedto require in order to write an audit log entry. This value is used during clean upprocessing to allow threads to complete their work before interrupting them. If abackground thread has not completed its work within the time allotted by thethreadlifespan parameter, then upon clean up processing, the thread will beinterrupted.ExamplesTo set the expected time a thread to write to the audit log should require to 10seconds, specify:Audit.handler.file.threadlifespan=10Audit Record FormatAll audit records use a similar output format which is described here. All auditrecords contain some common information including timestamp and record type,along with information specific to the audit event which occurred. The generalformat for audit records is shown here:AuditRecordType:[timestamp=timestampAttribute Name=Attribute Value...]Each record spans multiple lines in the file, with the first line of the recordbeginning with the audit record type beginning at the first character on the line,followed by a colon (;) and an opening left bracket ([). Subsequent lines associatedwith the same audit record are indented two (2) spaces to assist in readability ofthe log records. The last line for a single audit record contains a closing right7-4 Dell Encryption Key Mgr User's Guide
