1 .TH SLAPADD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
3 .\" Copyright 1998-2005 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapadd \- Add entries to a SLAPD database
22 is used to add entries specified in LDAP Directory Interchange Format
26 It opens the given database determined by the database number or
27 suffix and adds entries corresponding to the provided LDIF to
28 the database. The LDIF input is read from standard input or
33 is designed to accept LDIF in database order, as produced by
35 it does not verify that superior entries exist before
36 adding an entry, does not perform all user and system
37 schema checks, and does not maintain operational
38 attributes (such as createTimeStamp and modifiersName).
45 enable continue (ignore errors) mode.
48 enable dry-run (don't write to backend) mode.
51 enable quick (fewer integrity checks) mode. Does fewer consistency checks
52 on the input data, and no consistency checks when writing the database.
53 Improves the load time but if any errors or interruptions occur the resulting
54 database will be unusable.
57 write syncrepl context information.
58 After all entries are added, the contextCSN
59 will be updated with the greatest CSN in the database.
62 enable debugging messages as defined by the specified
66 Use the specified \fIsuffix\fR to determine which database to
67 add entries to. The \-b cannot be used in conjunction
73 Add entries to the \fIdbnum\fR\-th database listed in the
74 configuration file. The
76 cannot be used in conjunction with the
81 specify an alternative
86 Read LDIF from the specified file instead of standard input.
91 when you do this to ensure consistency of the database.
94 may not provide naming or schema checks. It is advisable to
97 when adding new entries into an existing directory.
99 To import the entries specified in file
103 database give the command:
107 SBINDIR/slapadd -l ldif
117 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
120 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
122 is derived from University of Michigan LDAP 3.3 Release.