Bug 682897 - Allow max log size to be set when nsslapd-*-logmaxdiskspace is set to -1
Summary: Allow max log size to be set when nsslapd-*-logmaxdiskspace is set to -1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On: 504803
Blocks: 434915 389_1.3.0
TreeView+ depends on / blocked
 
Reported: 2011-03-07 22:20 UTC by Nathan Kinder
Modified: 2015-01-04 23:47 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.2.8-0.7.rc2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 504803
Environment:
Last Closed: 2011-05-19 12:42:36 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0533 0 normal SHIPPED_LIVE new package: 389-ds-base 2011-05-18 17:57:44 UTC

Comment 4 Chandrasekar Kannan 2011-04-17 19:23:03 UTC
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 12:42:36 UTC
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


Note You need to log in before you can comment on or make changes to this bug.