[Date Prev][Date Next]
Re: Access Control development and cn=config
- To: lukeh@PADL.COM
- Subject: Re: Access Control development and cn=config
- From: Leif Johansson <firstname.lastname@example.org>
- Date: Fri, 25 Apr 2003 22:38:52 +0200
- Cc: Kurt@OpenLDAP.org, email@example.com, openldap-devel@OpenLDAP.org
- In-reply-to: <200303250704.SAA29201@au.padl.com>
- References: <firstname.lastname@example.org> <email@example.com> <200303250704.SAA29201@au.padl.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Luke Howard wrote:
I had the same approach with tyr (my all but dead-and-buried directory
Is there any standard for "exploded" LDIF on the filesystem yet?No. But one could just name each LDIF file using the UUID
of the entry and drop them all in one directory.
I think ISODE had a filesystem layout that resembled the DIT.
OTOH, iPlanet stores its LDIF configuration in a single file (perhaps
with the option to include others).
code). I did't have any backends just a single VFS-like "dit-system"
configuration and root-dse "volumes" were mounted when the server starts.
It worked very well for me.