Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 92

Audit.handler.file.multithreads, Audit.handler.file.threadlifespan, Audit Record Format, Syntax, Usage

Get Dell PowerVault TL4000 PDF manuals and user guides View all Dell PowerVault TL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 92 highlights

Audit.handler.file.multithreads Syntax Audit.handler.file.multithreads={yes|true|no|false} Usage If specified as true, then a separate thread is used to write the event data to the audit log, allowing the current thread of execution (operation) to continue without waiting for the write to the audit log to complete. Use of multiple threads is the default behavior. Examples An example setting the base name to true is: Audit.handler.file.multithreads=true Audit.handler.file.threadlifespan Syntax Audit.handler.file.threadlifespan=timeInSeconds Usage This parameter is used to specify the maximum time a thread should be expected to require in order to write an audit log entry. This value is used during clean up processing to allow threads to complete their work before interrupting them. If a background thread has not completed its work within the time allotted by the threadlifespan parameter, then upon clean up processing, the thread will be interrupted. Examples To set the expected time a thread to write to the audit log should require to 10 seconds, specify: Audit.handler.file.threadlifespan=10 Audit Record Format All audit records use a similar output format which is described here. All audit records contain some common information including timestamp and record type, along with information specific to the audit event which occurred. The general format for audit records is shown here: AuditRecordType:[ timestamp=timestamp Attribute Name=Attribute Value ... ] Each record spans multiple lines in the file, with the first line of the record beginning with the audit record type beginning at the first character on the line, followed by a colon (;) and an opening left bracket ([). Subsequent lines associated with the same audit record are indented two (2) spaces to assist in readability of the log records. The last line for a single audit record contains a closing right 7-4 Dell Encryption Key Mgr User's Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
Audit.handler.file.multithreads
Syntax
Audit.handler.file.multithreads=
{
yes
|
true
|
no
|
false
}
Usage
If specified as
true
, then a separate thread is used to write the event data to the
audit log, allowing the current thread of execution (operation) to continue without
waiting for the write to the audit log to complete. Use of multiple threads is the
default behavior.
Examples
An example setting the base name to
true
is:
Audit.handler.file.multithreads=true
Audit.handler.file.threadlifespan
Syntax
Audit.handler.file.threadlifespan=
timeInSeconds
Usage
This parameter is used to specify the maximum time a thread should be expected
to require in order to write an audit log entry. This value is used during clean up
processing to allow threads to complete their work before interrupting them. If a
background thread has not completed its work within the time allotted by the
threadlifespan parameter, then upon clean up processing, the thread will be
interrupted.
Examples
To set the expected time a thread to write to the audit log should require to 10
seconds, specify:
Audit.handler.file.threadlifespan=10
Audit Record Format
All audit records use a similar output format which is described here. All audit
records contain some common information including timestamp and record type,
along with information specific to the audit event which occurred. The general
format for audit records is shown here:
AuditRecordType
:[
timestamp=
timestamp
Attribute Name
=
Attribute Value
...
]
Each record spans multiple lines in the file, with the first line of the record
beginning with the audit record type beginning at the first character on the line,
followed by a colon (;) and an opening left bracket ([). Subsequent lines associated
with the same audit record are indented two (2) spaces to assist in readability of
the log records. The last line for a single audit record contains a closing right
7-4
Dell Encryption Key Mgr User's Guide