Bug 682897

Summary: Allow max log size to be set when nsslapd-*-logmaxdiskspace is set to -1
Product: Red Hat Enterprise Linux 6 Reporter: Nathan Kinder <nkinder>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Chandrasekar Kannan <ckannan>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: benl, dpal, jgalipea, kevinu, tamarinp
Target Milestone: rcKeywords: screened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-base-1.2.8-0.7.rc2.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 504803 Environment:
Last Closed: 2011-05-19 08:42:36 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 504803    
Bug Blocks: 434915, 495079    

Comment 4 Chandrasekar Kannan 2011-04-17 15:23:03 EDT
verified with 389-ds-base-1.2.8.2-1.el6.i686

[root@ds90-rhel6-32vm ~]# cat a.ldif
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-logmaxdiskspace
nsslapd-errorlog-logmaxdiskspace: -1

[root@ds90-rhel6-32vm ~]# /usr/lib/mozldap/ldapmodify -h localhost -p 389 -D "cn=directory manager" -w Secret123 -vcf ./a.ldif 
ldapmodify: started Sun Apr 17 15:19:25 2011

ldap_init( localhost, 389 )
replace nsslapd-errorlog-logmaxdiskspace:
	-1
modifying entry cn=config
modify complete

[root@ds90-rhel6-32vm ~]# cat a.ldif
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-maxlogsize
nsslapd-errorlog-maxlogsize: 101
[root@ds90-rhel6-32vm ~]# 


[root@ds90-rhel6-32vm ~]# /usr/lib/mozldap/ldapmodify -h localhost -p 389 -D "cn=directory manager" -w Secret123 -vcf ./a.ldif 
ldapmodify: started Sun Apr 17 15:20:36 2011

ldap_init( localhost, 389 )
replace nsslapd-errorlog-maxlogsize:
	101
modifying entry cn=config
modify complete

[root@ds90-rhel6-32vm ~]#
Comment 5 errata-xmlrpc 2011-05-19 08:42:36 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0533.html