2 .\" Copyright 1998-2004 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
4 .TH SLAPD 8C "RELEASEDATE" "OpenLDAP LDVERSION"
6 slapd \- Stand-alone LDAP Daemon
11 .B [\-f slapd\-config\-file]
13 .B [\-n service\-name] [\-s syslog\-level] [\-l syslog\-local\-user]
15 .B [\-u user] [\-g group] [\-t]
21 is the stand-alone LDAP daemon. It listens for LDAP connections on
22 any number of ports (default 389), responding
23 to the LDAP operations it receives over these connections.
25 is typically invoked at boot time, usually out of
29 normally forks and disassociates itself from the invoking tty.
31 .BR ETCDIR/slapd.conf ,
34 process will print its process ID (see
38 file, as well as the command line options during invocation to an
44 flag is given, even with a zero argument,
46 will not fork and disassociate from the invoking tty.
49 can be configured to provide replicated service for a database with
52 the standalone LDAP update replication daemon.
57 See the "OpenLDAP Administrator's Guide" for more details on
62 Listen on IPv4 addresses only.
65 Listen on IPv6 addresses only.
67 .BI \-d " debug\-level"
68 Turn on debugging as defined by
70 If this option is specified, even with a zero argument,
72 will not fork or disassociate from the invoking terminal. Some general
73 operation and status messages are printed for any value of \fIdebug\-level\fP.
74 \fIdebug\-level\fP is taken as a bit string, with each bit corresponding to a
75 different kind of debugging information. See <ldap.h> for details.
76 Remember that if you turn on packet logging, packets containing bind passwords
77 will be output, so if you redirect the log to a logfile, that file should
80 .BI \-s " syslog\-level"
83 at what level debugging statements should be logged to the
87 .BI \-n " service\-name"
88 Specifies the service name for logging and other purposes. Defaults
89 to basename of argv[0], i.e.: "slapd".
91 .BI \-l " syslog\-local\-user"
92 Selects the local user of the
94 facility. Values can be
101 However, this option is only permitted on systems that support
106 .BI \-f " slapd\-config\-file"
107 Specifies the slapd configuration file. The default is
108 .BR ETCDIR/slapd.conf .
112 will by default serve
114 (LDAP over TCP on all interfaces on default LDAP port). That is,
115 it will bind using INADDR_ANY and port 389.
118 option may be used to specify LDAP (and other scheme) URLs to serve.
119 For example, if slapd is given
120 .B "\-h \(dqldap://127.0.0.1:9009/ ldaps:/// ldapi:///\(dq",
121 It will bind 127.0.0.1:9009 for LDAP, 0.0.0.0:636 for LDAP over TLS,
122 and LDAP over IPC (Unix domain sockets). Host 0.0.0.0 represents
124 A space separated list of URLs is expected. The URLs should be of
125 LDAP (ldap://) or LDAP over TLS (ldaps://) or LDAP over IPC (ldapi://)
126 scheme without a DN or other optional parameters, except an experimental
127 extension to indicate the permissions of the underlying listeners.
128 Support for the latter two schemes depends on selected configuration
129 options. Hosts may be specified by name or IPv4 and IPv6 address formats.
130 Ports, if specified, must be numeric. The default ldap:// port is 389
131 and the default ldaps:// port is 636.
132 The socket permissions for LDAP over IPC are indicated by
133 "x-mod=-rwxrwxrwx", "x-mod=0777" or "x-mod=777", where any
134 of the "rwx" can be "-" to suppress the related permission (note,
135 however, that sockets only honor the "w" permission), while any
136 of the "7" can be any legal octal digit, according to chmod(1).
137 While LDAP over IPC requires write permissions on the socket to allow
138 any operation, the other listeners can take advantage of the "x-mod"
139 extension to apply rough limitations to users, e.g. allow read operations
140 ("r", which applies to search and compare), write operations ("w",
141 which applies to add, delete, modify and modrdn), and execute operations
142 ("x", which means bind is required).
143 "User" permissions apply to bound users, while "other" apply
147 Specifies a chroot "jail" directory. slapd will
151 to this directory after opening listeners but before reading
152 any configuration file or initializing any backend.
156 will run slapd with the specified user name or id, and that user's
157 supplementary group access list as set with initgroups(3). The group ID
158 is also changed to this user's gid, unless the -g option is used to
163 will run with the specified group name or id.
165 Note that on some systems, running as a non-privileged user will prevent
166 passwd back-ends from accessing the encrypted passwords. Note also that
167 any shell back-ends will run as the specified non-privileged user.
171 will read the configuration file (the default if none is given with the
172 \fI\-f\fP switch) and check its syntax, without opening any listener
176 This option provides a cookie for the syncrepl replication consumer.
177 The cookie is a comma separated list of name=value pairs.
178 Currently supported syncrepl cookie fields are
184 is the commit sequence number received by a previous synchronization
185 and represents the state of the consumer replica content which the
186 syncrepl engine will synchronize to the current provider content.
188 is the identity of the per-scope session log with which the
189 provider server can process this syncrepl request to reduce
190 synchronization traffic.
192 identifies a replication thread within the consumer server
193 and is used to find the syncrepl specification in
195 having the matching replication identifier in its definition.
199 and have it fork and detach from the terminal and start serving
200 the LDAP databases defined in the default config file, just type:
210 with an alternate configuration file, and turn
211 on voluminous debugging which will be printed on standard error, type:
215 LIBEXECDIR/slapd -f /var/tmp/slapd.conf -d 255
219 To test whether the configuration file is correct or not, type:
230 .BR slapd.access (5),
233 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
235 See http://www.openldap.org/its/
238 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
240 is derived from University of Michigan LDAP 3.3 Release.