1 .TH SLAPADD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2013 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapadd \- Add entries to a SLAPD database
14 .BI \-d \ debug-level\fR]
16 .BI \-f \ slapd.conf\fR]
24 .BI \-l \ ldif-file\fR]
28 .BI \-o \ option\fR[ = value\fR]]
44 is used to add entries specified in LDAP Directory Interchange Format
48 It opens the given database determined by the database number or
49 suffix and adds entries corresponding to the provided LDIF to
51 Databases configured as
53 of this one are also updated, unless \fB\-g\fP is specified.
54 The LDIF input is read from standard input or the specified file.
56 All files eventually created by
58 will belong to the identity
60 is run as, so make sure you either run
62 with the same identity
64 will be run as (see option
68 or change file ownership before running
71 Note: slapadd will also perform the relevant indexing whilst adding the database if
72 any are configured. For specfic details, please see
77 Use the specified \fIsuffix\fR to determine which database to
78 add entries to. The \fB\-b\fP cannot be used in conjunction
84 enable continue (ignore errors) mode.
87 enable debugging messages as defined by the specified
94 specify an alternative
99 specify a config directory.
104 are specified, the config file will be read and converted to
105 config directory format and written to the specified directory.
106 If neither option is specified, an attempt to read the
107 default config directory will be made before trying to use the default
108 config file. If a valid config directory exists then the
109 default config file is ignored. If dry-run mode is also specified,
110 no conversion will occur.
113 disable subordinate gluing. Only the specified database will be
114 processed, and not its glued subordinates (if any).
117 Jump to the specified line number in the LDIF file before processing
118 any entries. This allows a load that was aborted due to errors in the
119 input LDIF to be resumed after the errors are corrected.
122 Read LDIF from the specified file instead of standard input.
125 Add entries to the \fIdbnum\fR-th database listed in the
126 configuration file. The
128 cannot be used in conjunction with the
131 To populate the config database
132 .BR slapd\-config (5),
135 as it is always the first database. It must physically exist
136 on the filesystem prior to this, however.
138 .BI \-o \ option\fR[ = value\fR]
143 Possible generic options/values are:
146 syslog=<subsystems> (see `\-s' in slapd(8))
147 syslog\-level=<level> (see `\-S' in slapd(8))
148 syslog\-user=<user> (see `\-l' in slapd(8))
150 schema-check={yes|no}
154 The \fIschema\-check\fR option toggles schema checking (default on);
155 the \fIvalue\-check\fR option toggles value checking (default off).
156 The latter is incompatible with \fB-q\fR.
159 enable quick (fewer integrity checks) mode. Does fewer consistency checks
160 on the input data, and no consistency checks when writing the database.
161 Improves the load time but if any errors or interruptions occur the resulting
162 database will be unusable.
165 disable schema checking. This option is intended to be used when loading
166 databases containing special objects, such as fractional objects on a
167 partial replica. Loading normal objects which do not conform to
168 schema may result in unexpected and ill behavior.
171 Server ID to use in generated entryCSN. Also used for contextCSN
172 if \fB\-w\fP is set as well. Defaults to \fB0\fP.
175 enable dry-run (don't write to backend) mode.
181 write syncrepl context information.
182 After all entries are added, the contextCSN
183 will be updated with the greatest CSN in the database.
187 should not be running
188 when you do this to ensure consistency of the database.
191 may not provide naming or schema checks. It is advisable to
194 when adding new entries into an existing directory.
196 To import the entries specified in file
200 database give the command:
204 SBINDIR/slapadd \-l ldif
215 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)