[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Changing maximun number of locker entries

Howard Chu wrote:

-----Original Message-----
From: owner-openldap-software@OpenLDAP.org
[mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Andreas





On Thu, Jul 03, 2003 at 07:10:52PM +0200, Jorge Izquierdo wrote:


I can see the value is still 1000:

1000    Maximum number of lockers possible.

What´s the right way to change this value. Can anybody help


me showing


me the way to change such parameter?


This *may* be one of those parameters that are only taken into account
when creating a new database...



Yes. Stop slapd, then run db_recover; that will remove the current
environment. The next time slapd starts the new setting will take effect.

-- Howard Chu



Where is define "the environement" ? in each of the .bdb file ? db_recover resets it ? there's no harm running db_recover at any time ?
I did it while slapd was running ... then environement seemed to desepear/trash??

$ /usr/src/redhat/BUILD/openldap-2.1.22/db-instroot/bin/db_recover -v
db_recover: Finding last valid log LSN: file: 19 offset 6298826
db_recover: Recovery starting from [19][6298406]
db_recover: Recovery complete at Fri Jul 4 09:48:38 2003
db_recover: Maximum transaction ID 80000002 Recovery checkpoint [19][6299001]
db_recover: Recovery complete at Fri Jul 4 09:48:38 2003
db_recover: Maximum transaction id 80000000 Recovery checkpoint [19][6299001]
[root@corbeau /var/lib/ldap/int]
$ /usr/src/redhat/BUILD/openldap-2.1.22/db-instroot/bin/db_stat -c
db_stat: DB_ENV->open: No such file or directory


in sleepycat docs we can read "Because the *DB_CONFIG* file is read when the database environment is opened, it will silently overrule configuration done before that time."
When ?, the database environement is opened ? during slapadd and not at every slapd restart ?

thanks for these precisions, it will save me lot of time tuning/testing DB_CONFIG file parameters .