On Wed, 2012-02-08 at 21:28 +0100, Marco Pizzoli wrote:
As far as I can see, ldbedit is a raw datafile editor. Indeed I find
that I can manipulate the index definitions.
In what way can this help me in having a logic/tree visualization of
It doesn't let you visualize a tree, but it makes it easier to
read/modify objects in batch.
Another couple of questions on this topic:
- ldb files are concurrency safe? What if I ldbmodify a file.ldb while
it is already open by (let's say) another ldbmodify?
Yes ldb files use both locking and transactions and can be safely
modified by multiple processes at the same time.
We indeed rely on that property, as you can see our ldb files are opened
by multiple processes (providers and responders simultaneously).
- *just for experimenting*: is there a native way to possibly import
the ldif produced from ldbsearch in a real LDAP server? Does native
standard ldap schemas permit me to import/ldapadd objectClasses used
by sssd ldb?
ldb will produce a valid ldif file, but it is schemaless.
In order to be able to import those ldif file in an actual ldap server
you need to be able to disable schema checking on the server.
Simo Sorce * Red Hat, Inc * New York