2.3.1.31
This attribute sets the maximum audit log size in megabytes. When this value is reached, the audit log is rotated. That means the server starts writing log information to a new log file. If
When setting a maximum log size, consider the total number of log files that can be created due to log file rotation. Also, remember that there are three different log files (access log, audit log, and error log) maintained by the Directory Server, each of which consumes disk space. Compare these considerations to the total amount of disk space for the audit log.
Parameter | Description |
Entry DN | cn=config |
|
|
Valid Range | |
| file is unlimited in size. |
|
|
Default Value | 100 |
|
|
Syntax | Integer |
|
|
Example | |
|
|
2.3.1.32
This attribute sets the total number of audit logs that can be contained in the directory where the audit log is stored. Each time the audit log is rotated, a new log file is created. When the number of files contained in the audit log directory exceeds the value stored on this attribute, then the oldest version of the log file is deleted. The default is 1 log. If this default is accepted, the server will not rotate the log, and it grows indefinitely.
If the value for this attribute is higher than 1, then check the
Parameter | Description |
Entry DN | cn=config |
|
|
Valid Range | 1 to the maximum |
|
|
Default Value | 1 |
|
|
Syntax | Integer |
|
|
Example | |
|
|
2.3.1.33
This attribute sets the access mode or file permissions with which audit log files are to be created. The valid values are any combination of 000 to 777 because they mirror numbered or absolute UNIX file permissions. The value must be a combination of a
Digit | Description | Digit | Description |
|
|
|
|
0 | None | 4 | Read only |
1 | Execute only | 5 | Read and execute |
|
|
|
|
2.3 Core server configuration attributes reference | 35 |