I'm looking at a Prometheus graph of cn=Read,cn=Waiters,cn=Monitor
The object class is monitorCounterObject, the attribute is called
If it's a counter I'd expect the value to only increase.
But the graph shows decreasing values!?!
What's the exact meaning of this?
How to profile performance of different ACLs?
In theory one could run slapd with debug symbols under control of a
profiler for C code. But personally I don't have a clue which ACL
processing entry points to examine more closely.
Another approach could be to derive metrics from acl-loglevel messages.
As far as I understood the MDB disk format changed. So the MDB files
have to be re-created (either by simply removing/replicating or
Now I'm wondering how to automate things (with ansible and puppet) in a
truly idempotent way. Ideally I could determine whether existing MDB
files were last maintained by OpenLDAP 2.4.x or whether they already
have the 2.5 format.
Can I find out the disk format version in any way, e.g. with python-lmdb?
I'm trying to plug LMDB into a system where the user first modifies the value, and only afterwards notifies me that the value has been changed. In LMDB I've been simply passing the value pointer received from mdb_cursor_get (db opened with MDB_WRITEMAP), and if the user notifies me that the value has been changed, I commit the write transaction.
Is this an acceptable use pattern? It seems to work (but crashes without MDB_WRITEMAP). Only thing vaguely related I could find here was https://www.openldap.org/lists/openldap-technical/201510/msg00016.html
Hi, There is a specific requirement where the client needs the memberOf attribute to be returned by default. As per the current design the memberOf attribute is of type operational and thus needs to be explicitly asked for. Is there a easy way to update the schema and change the type of the attribute from Operational to userApplication so that the attribute will be returned by default ? I tried to update the schema using a ldif file but I am getting the following error:- error code 80 - olcAttributeTypes: Duplicate attributeType: 1.2.840.1135184.108.40.206
Please assist with this request.
My Ldif is as follows:-
olcAttributeTypes: ( 1.2.840.1135220.127.116.11 NAME 'memberOf' DESC 'Group that the entry belongs to' EQUALITY distinguishedNameMatch SYNTAX 18.104.22.168.4.1.1422.214.171.124.12 USAGE dSAOperation X-ORIGIN 'iPlanet Delegated Administrator' )
olcAttributeTypes: ( 1.2.840.1135126.96.36.199 NAME 'memberOf' DESC 'Group that the entry belongs to' EQUALITY distinguishedNameMatch SYNTAX 188.8.131.52.4.1.14184.108.40.206.12 )
According to this post
http://blog.oddbit.com/post/2013-07-22-generating-a-membero/ it is possible
to use a strategy for generating a memberOf attribute for posixGroups
This need arose for a legacy OpenLDAP LDAP and with several applications
So, this seems to me the best solution to be able to use the memberOf as a
NOTE: Complete information about the problem here
*QUESTION:* Has anyone tested/used the procedure in the post
http://blog.oddbit.com/post/2013-07-22-generating-a-membero/ ? Ie,
generating a memberOf attribute for posixGroups (dynlist module)?
What I have for group OU and user OU is what goes below...
User Letter A
User Letter A
Tecnologia, Desenvolvimento e Software Livre
LightBase Consultoria em Software Público
*+55-61-3347-1949* - http://brlight.org <eduardo.lucio(a)LightBase.com.br> -
*Software livre! Abrace essa idéia! *
*"Aqueles que negam liberdade aos outros não a merecem para si mesmos."*