mirror of
https://git.openldap.org/openldap/openldap.git
synced 2025-01-06 10:46:21 +08:00
Further details as to why slapcat(8) output cannot be used
as generated with ldapadd(1).
This commit is contained in:
parent
2a5ecbccaa
commit
da29a69b7d
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user