Manpages

NAME

slapadd - Add entries to a SLAPD database

SYNOPSIS

/usr/sbin/slapadd [-b suffix] [-c] [-d debug-level] [-f slapd.conf] [-F confdir] [-g] [-j lineno] [-l ldif-file] [-n dbnum] [-o option[=value]] [-q] [-s] [-S SID] [-u] [-v] [-w]

DESCRIPTION

Slapadd is used to add entries specified in LDAP Directory Interchange Format (LDIF) to a slapd(8) database. It opens the given database determined by the database number or suffix and adds entries corresponding to the provided LDIF to the database. Databases configured as subordinate of this one are also updated, unless -g is specified. The LDIF input is read from standard input or the specified file.

All files eventually created by slapadd will belong to the identity slapadd is run as, so make sure you either run slapadd with the same identity slapd(8) will be run as (see option -u in slapd(8)), or change file ownership before running slapd(8).

Note: slapadd will also perform the relevant indexing whilst adding the database if any are configured. For specific details, please see slapindex(8).

OPTIONS

-b suffix

Use the specified suffix to determine which database to add entries to. By default, the first database that supports the requested operation is used. The -b cannot be used in conjunction with the -n option.

-d debug-level

enable debugging messages as defined by the specified debug-level; see slapd(8) for details.

-f slapd.conf

specify an alternative slapd.conf(5) file.

-F confdir

specify a config directory. If both -f and -F are specified, the config file will be read and converted to config directory format and written to the specified directory. If neither option is specified, an attempt to read the default config directory will be made before trying to use the default config file. If a valid config directory exists then the default config file is ignored. If dry-run mode is also specified, no conversion will occur.

-j lineno

Jump to the specified line number in the LDIF file before processing any entries. This allows a load that was aborted due to errors in the input LDIF to be resumed after the errors are corrected.

-l ldif-file

Read LDIF from the specified file instead of standard input.

-n dbnum

Add entries to the dbnum-th database listed in the configuration file. The -n cannot be used in conjunction with the -b option. To populate the config database slapd-config(5), use -n 0 as it is always the first database. It must physically exist on the filesystem prior to this, however.

-o option[=value]

Specify an option with a(n optional) value. Possible generic options/values are:

syslog=<subsystems> (see ’-s’ in slapd(8))
syslog-level=<level> (see ’-S’ in slapd(8))
syslog-user=<user> (see ’-l’ in slapd(8))

schema-check={yes|no}
value-check={yes|no}

The schema-check option toggles schema checking (default on);
the value-check option toggles value checking (default off).
The latter is incompatible with -q.

on the input data, and no consistency checks when writing the database.
Improves the load time but if any errors or interruptions occur the resulting
database will be unusable.

databases containing special objects, such as fractional objects on a
partial consumer. Loading normal objects which do not conform to
schema may result in unexpected and ill behavior.

if -w is set as well. Defaults to 0.

After all entries are added, the contextCSN
will be updated with the greatest CSN in the database.

LIMITATIONS

Your slapd(8) should not be running when you do this to ensure consistency of the database.

slapadd may not provide naming or schema checks. It is advisable to use ldapadd(1) when adding new entries into an existing directory.

EXAMPLES

To import the entries specified in file ldif into your slapd(8) database give the command:

SEE ALSO

ldap(3), ldif(5), slapcat(8), slapindex(8), slapmodify(8), ldapadd(1), slapd(8)

"OpenLDAP Administrator’s Guide" (http://www.OpenLDAP.org/doc/admin/)

ACKNOWLEDGEMENTS

OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>;. OpenLDAP Software is derived from the University of Michigan LDAP 3.3 Release.