From: Kurt Zeilenga <kurt@openldap.org>
Date: Wed, 3 May 2006 16:51:45 +0000 (+0000)
Subject: Further details as to why slapcat(8) output cannot be used
X-Git-Tag: OPENLDAP_REL_ENG_2_4_1ALPHA~2^2~86
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=da29a69b7d20f937a3e0234da15bb1f3dd189f90;p=openldap

Further details as to why slapcat(8) output cannot be used
as generated with ldapadd(1).
---

diff --git a/doc/man/man8/slapcat.8 b/doc/man/man8/slapcat.8
index 3cba0bb719..4f80335d66 100644
--- a/doc/man/man8/slapcat.8
+++ b/doc/man/man8/slapcat.8
@@ -33,12 +33,19 @@ Databases configured as
 .B subordinate
 of this one are also output, unless \fB-g\fP is specified.
 .LP
-The LDIF generated by this tool is suitable for use with
+The entry records are presented in database order, not superior first
+order.  The entry records will include all (user and operational)
+attributes stored in the database.  The entry records will not include
+dynamically generated attributes (such as subschemaSubentry).
+.LP
+The output of slapcat is intended to be used as input to
 .BR slapadd (8).
-As the entries are in database order, not superior first order,
-they cannot be loaded with
+The output of slapcat cannot generally be used as input to
 .BR ldapadd (1)
-without first being reordered.
+or other LDAP clients without first editing the output.
+This editing would normally include reordering the records
+into superior first order and removing no-user-modification
+operational attributes.
 .SH OPTIONS
 .TP
 .B \-v