Im trying to load this schema
And I get this error.
ldapmodify: invalid format (line 1) entry: ""
Googling around I found that I need to add ( : ) after the attribute
and that's wha I did, now Im getting the error in line 3 but adding
the (: ) in the objectclass: did not help
ldapmodify: invalid format (line 3) entry: ""
Any help appreciated
Is there a recommended way to discontinue the use of the ppolicy overlay?
The only way I've found that works is to stop the ldap server and using slapcat/edit/slapadd eradicate all the ppolicy attributes (combined with removing the ppolicy overlay and schema from the slapd.conf file).
I'm attempting this on RHEL7 with OpenLDAP 2.4.46 (local built).
Anybody have any idea on how to have the database file
grow until you get to the mapsize instead of pre-allocating the entire
mapsize (4GB) upon initialization?
I don't mind having an upper limit on the map size, but I think it
would be helpful
to have it grow to the upper limit, not preallocate the space on storage.
There are various areas in the documentation where it talks about
having the database not grow without bounds.
due to the fact that some software libraries are lacking full support
of Lightweight Directory Access Protocol according to RFC-4510 and that
openLDAP.js, a wrapper of libldap, has been developed.
The library has been published under MIT-Licence and is available at
Dieter Klünter | Systemberatung
GPG Key ID: E9ED159B
I'm trying to install node-lmdb on Windows 8.1 (which uses node-gyp to
handle LMDB compilation) but it fails with the following error:
..\dependencies\lmdb\libraries\liblmdb\mdb.c(55): error C2059: syntax
error: '(' [C:\Users\Foo\Downloads\node-lmdb\node
(The whole error log is available here).
Looking around the git repository, there seems to be a recent change in
that part of the code, so I manually checked out to the commit just
before that change and that seemed to enable successful compilation.
Is there anything I'm doing wrong? Is there any documentation I can read
about the correct way to compile LMDB in Windows?
Jeffrey Esquivel S.
I'm trying to implement a LDAP client. I see that functions like
ldap_search_ext_s() may dynamically allocate memory.
Is there a way to supply my own memory allocation functions for
open-ldap API? I'm asking because I would like to allocate memory
during initialization, not during run time.
Else, how can I calculate the max amount of memory that such calls
will require? What should happen if not enough memory is available
when a function like ldap_search_ext_s() gets called? Is there a
special error code that indicates that?