Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 72 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here






       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.


       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>  minutes  have  passed  since the last check­
              point.  Both arguments default to  zero,  in  which
              case  they are ignored.  See the Berkeley DB refer­
              ence guide for more details.

              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 contain­
              ing this database and associated indexes  live.   A
              separate  directory  must  be  specified  for  each
              database.  The default is  /var/run/slapd/openldap-

              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 performance, but may also return
              inconsistent  results  if  the  data  comes  from a
              transaction that is later aborted.  In  this  case,
              cial 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  slapin­

       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

       searchstack <depth>
              Specify the depth of the stack used for search fil­
              ter  evaluation.  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 addi­
              tional memory allocation. Filters that  are  nested
              deeper  than  the  search  stack depth will cause a
              separate stack to be allocated for that  particular
              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.


              default slapd configuration file


       slapd.conf(5), slapd(8), slapadd(8),  slapcat(8),  slapin­

OpenLDAP 2.1.22             06-26-2003               SLAPD-BDB(5)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =




Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can help in many different ways.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds