Howard Chu writes:
You could give back-ldif a try. It certainly will not perform well, but it's
so simple that data corruption wouldn't be an issue.
Actually it can leave behind a temporary file if you pull the plug on
slapd at just the wrong moment, when an entry is being written. That
won't
On Sat, Dec 18, 2010 at 4:04 PM, Howard Chu h...@symas.com wrote:
Bruce Edge wrote:
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
plambrecht...@gmail.com wrote:
Or perhaps TinyLdap? http://www.fefe.de/tinyldap/
Also FreeRadius (if your app's support Radius and LDAP) supports a
Am Sun, 19 Dec 2010 08:02:02 -0800
schrieb Bruce Edge bruce.e...@gmail.com:
On Sat, Dec 18, 2010 at 4:04 PM, Howard Chu h...@symas.com wrote:
Bruce Edge wrote:
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
plambrecht...@gmail.com wrote:
Or perhaps TinyLdap?
On Sun, Dec 19, 2010 at 9:12 AM, Dieter Kluenter die...@dkluenter.de wrote:
Am Sun, 19 Dec 2010 08:02:02 -0800
schrieb Bruce Edge bruce.e...@gmail.com:
On Sat, Dec 18, 2010 at 4:04 PM, Howard Chu h...@symas.com wrote:
Bruce Edge wrote:
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
On Sat, Dec 18, 2010 at 12:19 AM, Peter Lambrechtsen
plambrecht...@gmail.com wrote:
Why don't you use SQLite instead??? It's pretty rock solid backend database.
Unless your client side only wants to talk LDAP.
Hi,
Thanks the the response. One of the reasons for ldap is that it
handles all the
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
plambrecht...@gmail.com wrote:
Or perhaps TinyLdap? http://www.fefe.de/tinyldap/
Also FreeRadius (if your app's support Radius and LDAP) supports a myriad of
backend databases.
Hmm, very interesting. I was not aware of this project.
My
Bruce Edge wrote:
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
plambrecht...@gmail.com wrote:
Or perhaps TinyLdap? http://www.fefe.de/tinyldap/
Also FreeRadius (if your app's support Radius and LDAP) supports a myriad of
backend databases.
Hmm, very interesting. I was not aware of
Perhaps a bit more detail...
During testing our developers frequently hang the target machines.
This usually results in a corrupted ldap database even though no write
activity was present on the box since long before the crash.
What ldap config tuning options are required to get slapd to sync the
I'm working on an embedded system for which I would like to use
openldap as the means of config storage.
I've spent a lot of time RTFM'ing and still feel that there is a lot
that is escaping me as far as the optimal configuration.
If the primary goal is data safety and zero human intervention,
