From: Howard Chu <hyc@openldap.org>
Date: Wed, 20 Dec 2006 14:25:06 +0000 (+0000)
Subject: Cleanup, document include: extension
X-Git-Tag: OPENLDAP_REL_ENG_2_4_4ALPHA~8^2~331
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=065ea81f307d35a812dfc86be941123ba4c3fa68;p=openldap

Cleanup, document include: extension
---

diff --git a/doc/man/man5/ldif.5 b/doc/man/man5/ldif.5
index 7eb51e3c1a..3a5b77784e 100644
--- a/doc/man/man5/ldif.5
+++ b/doc/man/man5/ldif.5
@@ -7,8 +7,13 @@ ldif \- LDAP Data Interchange Format
 .SH DESCRIPTION
 The LDAP Data Interchange Format (LDIF) is used to represent LDAP
 entries and change records in text form. LDAP tools, such as
-.BR ldapadd (1) and .BR ldapsearch (1), read and write LDIF entry
-records.  ldapmodify(1) reads LDIF change records.
+.BR ldapadd (1)
+and
+.BR ldapsearch (1),
+read and write LDIF entry
+records.
+.BR ldapmodify (1)
+reads LDIF change records.
 .LP
 This manual page provides a basic description of LDIF.  A
 formal specification of LDIF is published in RFC 2849.
@@ -228,11 +233,36 @@ of each type of change.
 	changetype: delete
 .fi
 
+.SH INCLUDE STATEMENT
+The LDIF parser has been extended to support an
+.B include
+statement for referencing other LDIF files.  The
+.B include
+statement must be separated from other records by a blank line.
+The referenced file is specified using a file: URI and all of its
+contents are incorporated as if they were part of the original
+LDIF file. As above, other URI schemes may be supported. For example:
+.LP
+.nf
+	dn: dc=example,dc=com
+	objectclass: domain
+	dc: example
+
+	include: file:///tmp/example.com.ldif
+
+	dn: dc=example,dc=org
+	objectclass: domain
+	dc: example
+.fi
+This feature is not part of the LDIF specification in RFC 2849 but
+is expected to appear in a future revision of this spec.
+
 .SH SEE ALSO
 .BR ldap (3),
 .BR ldapsearch (1),
 .BR ldapadd (1),
 .BR ldapmodify (1),
+.BR slapadd (8),
 .BR slapd.replog (5).
 .LP
 "LDAP Data Interchange Format," Good, G., RFC 2849.