slapd-bdb man page on OpenDarwin

Man page or keyword search:  
man Server   3202 pages
apropos Keyword Search (all sections)
Output format
OpenDarwin logo
[printable version]

SLAPD-BDB(5)							  SLAPD-BDB(5)

NAME
       slapd-bdb - BDB backend to slapd

SYNOPSIS
       /etc/openldap/slapd.conf

DESCRIPTION
       The  BDB	 backend  to  slapd(8) is the recommended backend for a normal
       slapd database.	It uses the Sleepycat BerkelyDB package to store data.
       It makes extensive use of indexing and caching to speed data access.

CONFIGURATION
       These  slapd.conf  options apply to the BDB backend database.  That is,
       they must follow a "database bdb" line and come before  any  subsequent
       "backend" or "database" lines.  Other database options are described in
       the slapd.conf(5) manual page.

       cachesize <integer>
	      Specify the size in entries of the in-memory cache maintained by
	      the BDB backend database instance.  The default is 1000 entries.

       checkpoint <kbyte> <min>
	      Specify the frequency for checkpointing the database transaction
	      log.  A checkpoint operation flushes  the	 database  buffers  to
	      disk  and writes a checkpoint record in the log.	The checkpoint
	      will occur if either <kbyte> data has been written or <min> min‐
	      utes  have  passed  since	 the  last checkpoint.	Both arguments
	      default to zero, in which case they are ignored.	See the Berke‐
	      ley DB reference guide for more details.

       dbnosync
	      Specify that on-disk database contents should not be immediately
	      synchronized with in memory changes.  Enabling this  option  may
	      improve performance at the expense of data security.

       directory <directory>
	      Specify  the directory where the BDB files containing this data‐
	      base and associated indexes live.	 A separate directory must  be
	      specified	 for  each  database.	The  default is /var/db/openl‐
	      dap/openldap-data.

       dirtyread
	      Allow reads of modified but not  yet  committed  data.   Usually
	      transactions  are	 isolated  to  prevent	other  operations from
	      accessing uncommitted data.  This	 option	 may  improve  perfor‐
	      mance,  but  may	also  return  inconsistent results if the data
	      comes from a transaction that is later aborted.  In  this	 case,
	      the  modified  data  is  discarded  and a subsequent search will
	      return a different result.

       index {<attrlist>|default} [pres,eq,approx,sub,<special>]
	      Specify the indexes to maintain for the given attribute (or list
	      of  attributes).	 Some  attributes  only	 support  a  subset of
	      indexes.	If only an <attr> is given, the indices specified  for
	      default  are  maintained.	  Note that setting a default does not
	      imply that all attributes will be indexed.

	      A number of special index	 parameters  may  be  specified.   The
	      index  type  sub	can be decomposed into subinitial, subany, and
	      subfinal indices.	 The special type nolang may be	 specified  to
	      disallow	use  of	 this index by language subtypes.  The special
	      type nosubtypes may be specified to disallow use of  this	 index
	      by  named	 subtypes.   Note:  changing  index  settings requires
	      rebuilding indices, see slapindex(8).

       lockdetect {oldest|youngest|fewest|random|default}
	      Specify which transaction to abort when a deadlock is  detected.
	      The default is the same as random.

       mode <integer>
	      Specify  the  file  protection  mode that newly created database
	      index files should have.	The default is 0600.

       searchstack <depth>
	      Specify the depth of the stack used for  search  filter  evalua‐
	      tion.   Search  filters  are  evaluated on a stack to accomodate
	      nested AND / OR clauses. An individual stack is assigned to each
	      server  thread.  The depth of the stack determines how complex a
	      filter can be evaluated without requiring any additional	memory
	      allocation. Filters that are nested deeper than the search stack
	      depth will cause a separate stack to be allocated for that  par‐
	      ticular  search  operation.  These  allocations can have a major
	      negative impact on server performance, but specifying  too  much
	      stack  will  also	 consume  a great deal of memory.  Each search
	      stack uses 512K bytes per level. The default stack depth is  16,
	      thus 8MB per thread is used.

FILES
       /etc/openldap/slapd.conf
	      default slapd configuration file

SEE ALSO
       slapd.conf(5), slapd(8), slapadd(8), slapcat(8), slapindex(8).

OpenLDAP 2.1.X			  RELEASEDATE			  SLAPD-BDB(5)
[top]

List of man pages available for OpenDarwin

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
...................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net