Core Server Configuration Attributes Reference56 Netscape Directory Server Configuration, Command, and File Reference • May 2002nsslapd-errorlog-maxlogsize (Maximum Error Log Size)Specifies the maximum error log size in megabytes. When this value is reached, theerror log is rotated. That is, the server starts writing log information to a new logfile. If you set nsslapd-errorlog-maxlogsperdir to 1, the server ignores thisattribute.When setting a maximum log size, consider the total number of log files that can becreated due to log file rotation. Also remember that there are 3 different log files(access log, audit log, and error log) maintained by the Directory Server, each ofwhich will consume disk space. Compare these considerations to the total amountof disk space that you want to be used by the error log.nsslapd-errorlog-maxlogsperdir (Maximum Number of Error LogFiles)Specifies the total number of error logs that can be contained in the directory wherethe error log is stored. If you are using log file rotation, then each time the error logis rotated, a new log file is created. When the number of files contained in the errorlog directory exceeds the value stored on this attribute, then the oldest version ofthe log file is deleted. The default is 1 log. If you accept this default, the server willnot rotate the log and it will grow indefinitely.If the value for this attribute is higher than 1, then you need to check thensslapd-errorlog-logrotationtime attribute to establish whether or not logrotation is specified. If the nsslapd-errorlog-logrotationtime attribute has avalue of -1 then there is no log rotation. See “nsslapd-errorlog-logrotationtime(Error Log Rotation Time)” on page 55 for more information.Default Value: weekSyntax: DirectoryStringExample: nsslapd-errorlog-logrotationtimeunit: dayEntry DN: cn=configValid Range: -1 | 1 to the maximum 32 bit integer value (2147483647) where a valueof -1 means the log file is unlimited in size.Default Value: 100Syntax: IntegerExample: nsslapd-errorlog-maxlogsize: 100
