Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable support for Lightning Memory-Mapped Database Manager (LMDB) #10

Open
fbrehm opened this issue Feb 2, 2024 · 0 comments
Open

Comments

@fbrehm
Copy link

fbrehm commented Feb 2, 2024

Since 389-ds-base 2.1.0, The 389 ldap directory server supports two kind of underlying database:

  • Berkeley Database (BerkeleyDB)
  • Lightning Memory-Mapped Database Manager (LMDB)

Starting from version 3.0.0 New instances are no longer created with BerkeleyDB by default but with LMDB.

See FAQ about BerkeleyDB backend deprecation and using LMDB backend.

For 389-ds-base >= 2.1.0 and < 3.0.0 the resource ds_389::instance should provide an option for selecting the database engine. For this in creation of the template file for the instance in section [slapd] there should be a key/value pair with the key 'db_lib' and a value of either 'bdb' (BerkeleyDB) or 'mdb' (LMDB). The default value should be 'mdb'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant