[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
slapcat old and new + schema conflicts
- To: OpenLDAP <openldap-software@OpenLDAP.org>
- Subject: slapcat old and new + schema conflicts
- From: "matthew sporleder" <msporleder@gmail.com>
- Date: Thu, 13 Apr 2006 09:21:33 -0400
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=tNs0TW7wqYOd8I3POfGNKdL5FbQ95CFHF9dsbI1nRh4i0ZZVd2eHPXrKG4JlOsMZoktXNpTfNJEAQXQR9KeYyK77OL7BZkNsfUjlX7zTaLb6B7nheo0xjOJ2XvIz0Hq2lNe/KZ0HtUqcFIZASQW63bySCE9uUWmA2ciFIRZFXXs=
I am attempting to use slapcat to create an ldif of my 2.1 database.
When I use the modern (2.3.21) slapcat on my 2.1 database, it
complains about schema conflicts. The 2.1 version, however, does not
complain. (This is also true of slapd, which is a little more
expected)
Should I work on resolving these scehma conflicts and use the 2.3
slapcat, or will the 2.1 slapcat-generated-ldif be fine for the 2.3
slapadd if I resolve the conflicts with the config file/directory I'm
using for 2.3. (assuming I delete the entryCSN's)
slapcat(2.1) -f 2.1.config.conf -l output.ldif
slapadd(2.3) -f 2.3.config.conf