[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Filesystem & backend options for embedded openldap

Bruce Edge wrote:
On Sat, Dec 18, 2010 at 12:26 PM, Peter Lambrechtsen
<plambrechtsen@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 concern is that there's been very little activity on the project in
recent years.

Is there no simple, reliable, backend config for openldap?

I'm not concerned with speed, just reliability and data integrity.

I'd settle for a 10x performance penalty for data integrity.

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.


On Sun, Dec 19, 2010 at 5:59 AM, Bruce Edge<bruce.edge@gmail.com>  wrote:

On Sat, Dec 18, 2010 at 12:19 AM, Peter Lambrechtsen
<plambrechtsen@gmail.com>  wrote:
Why don't you use SQLite instead??? It's pretty rock solid backend

Unless your client side only wants to talk LDAP.

Thanks the the response. One of the reasons for ldap is that it
handles all the authentication for a lot of the packages we're using
out of the box so it was a natural progression to extend it to handle
the other data we need as well.
The only probems, it appears, is how to make it more failsafe on the back


On Sat, Dec 18, 2010 at 6:48 AM, Bruce Edge<bruce.edge@gmail.com>

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
backend to a state where power loss / kernel crashes do not corrupt
the data?



On Wed, Dec 15, 2010 at 10:25 AM, Bruce Edge<bruce.edge@gmail.com>
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, what
would be the optimal combination of file system / backend storage /
and config options?

I would like to never have to manually recover a database and have it
gracefully recover from power failures. Speed is not an issue as it's
very low traffic. Integritiy is everything.
It's target storage is a USB flash device. Are there any special
considerations WRT flash storage and ldap?

Thanks in advance.


  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/