Re: How to add index for "member" of ldap groups

Am Donnerstag, 26. Januar 2017 22:17 CET, Axel Birndt schrieb: > [...] > > If i try to add a new index "olcdbindex: member pres,sub,eq" > > i got an failure > > Could not perform ldap_modify operation. > LDAP said: Other (e.g., implementation specific) error

How to add index for "member" of ldap groups

Hi @All, i'am currently searching for a possibility to add an index in openldap (cn=config backend) for the "member" of groups. In my log i got the following message: > 475 admin slapd: <= bdb_equality_candidates: (member) not indexed I found, that "member" is an attribute from an ldap

Re: Has anybody benchmarked OpenLDAP as an Object Storage Service?

John Lewis wrote: I am wondering if anybody has benchmarked OpenLDAP as a generic network object storage service. I know Networked Key Value Databases are getting more popular because they seem to scale laterally better. Probably nothing recent. Back in the CORBA days it was probably a

Re: fresh (distro's) installation and cn=config password

(Copy for the list) >>> Ulrich Windl schrieb am 24.01.2017 um >>> 13:19 in Nachricht <58875475.ed38.00a...@rz.uni-regensburg.de>: lejeczek schrieb am 23.01.2017 um 17:59 in Nachricht >

Has anybody benchmarked OpenLDAP as an Object Storage Service?

I am wondering if anybody has benchmarked OpenLDAP as a generic network object storage service. I know Networked Key Value Databases are getting more popular because they seem to scale laterally better. Most of the so called NoSQL databases use some kind of JSON over HTTPS network transport. I

RE: BDB Backend: How to force transaction log rotation for log archival based on db_archive

Hi, > Is there a way to force a transaction log rotation to make sure that even > changes that do not cause > a new transaction log to be created will get archived at regular intervals? It can be done but the scenario definitely requires code to do so. The internal function __log_newfile can

BDB Backend: How to force transaction log rotation for log archival based on db_archive

Hi, I use OpenLDAP with the Berkeley DB backend and db_archive to move unused transaction logs to a backup location for the purpose of disaster recovery. The intention is to reduce the data loss window to N minutes. Consequently, I execute db_archive every N minutes. If the transaction