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

Re: Filesystem & backend options for embedded openldap

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> wrote:
> 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.
> -Bruce