[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
HDB physical files separate from DIT
- To: OpenLDAP software list <openldap-software@OpenLDAP.org>
- Subject: HDB physical files separate from DIT
- From: matthew sporleder <msporleder@gmail.com>
- Date: Tue, 3 Jan 2006 09:06:36 -0500
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jxlZM/Fe+z2yKtjy951TMA5U1fxpY8oZp+h+Py6g6p4+7nguiatr3UWj9mfRM6v8e0FqGNcgO+4oiFg8YNFPSOijhSO/I1ke1pJqkz1k+CIcIchh4yrPMUqr/a4jyN11pcio7ROfencpMHddsrE9MfPo00llWbrorER+eFD7lW0=
I'm trying to figure out if I can abstract a database's logical layout
(DIT) from being bound to specific files per 'database' definition,
and I'm not seeing any good tips in the berkeley db tuning docs.
For example:
I have ou=region1,dc=example,dc=com and ou=region2,dc=exmaple,dc=com.
Right now the only options I see of separating these are to define
them in different 'database' sections. I would, however, like to have
them both defined in one database, but allow the actual database files
(dn2id, etc) to be split in terms of size, or other definables.
(usage stats, whatever)
Am I missing something obvious in DB_CONFIG like "max_file_size"?
Thanks,
_Matt