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

Re: (ITS#3702) [devel] back-config and back-ldap should be slapcat'able

quanah@stanford.edu wrote:

>Full_Name: Quanah Gibson-Mount
>Version: HEAD
>URL: ftp://ftp.openldap.org/incoming/
>Submission from: (NULL) (
>It should be possible to use slapcat to export your config database, and any
>"database ldif" defined database in your slapd.conf file.  Currently in head,
>slapcat will skip any "database ldif" definitions it finds.
This problem affected all of the slap tools. back-ldif did not send 
entries as soon as they were available, instead it enumerated the entire 
database tree and stored the entries in a list before sending them one 
by one. This mean that back-config did not get to process any of them 
until they were all read.

Unfortunately, in tool mode, str2entry tries to do a schema-aware 
validation of its input values. Since the schema entries had not yet 
been processed by back-config, any olcDatabase entry with olcSuffix set 
using RDNs whose attributes were not hardcoded would fail in the 
validation step when read by back-ldif. This has been fixed, back-ldif 
now sends entries as soon as it reads them, so that back-config can 
process them immediately and have their definitions available for 
subsequently read entries.

>On a related note, I'm not clear how one would "slapadd" a slapcat'd
>"back-config" DB?
back-config is accessed using '-n0' for slapadd/slapcat. e.g.
    slapadd -F testrun/slapd.d -l cf.ldif -n0

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support