---

   slapo-accesslog    ( 5 )

---

Конфигурация (Configuration)

These slapd.conf options apply to the Access Logging overlay.
       They should appear after the overlay directive.

       logdb <suffix>
              Specify the suffix of a database to be used for storing
              the log records.  The specified database must be defined
              elsewhere in the configuration and must support an ordered
              return of results such as slapd-mdb(5) The access controls
              on the log database should prevent general access. The
              suffix entry of the log database will be created
              automatically by this overlay. The log entries will be
              generated as the immediate children of the suffix entry.

       logops <operations>
              Specify which types of operations to log. The valid
              operation types are abandon, add, bind, compare, delete,
              extended, modify, modrdn, search, and unbind. Aliases for
              common sets of operations are also available:

              writes add, delete, modify, modrdn

              reads  compare, search

              session
                     abandon, bind, unbind

              all    all operations

       logbase <operations> <baseDN>
              Specify a set of operations that will only be logged if
              they occur under a specific subtree of the database. The
              operation types are as above for the logops setting, and
              delimited by a '|' character.

       logold <filter>
              Specify a filter for matching against Deleted and Modified
              entries. If the entry matches the filter, the old contents
              of the entry will be logged along with the current
              request.

       logoldattr <attr> ...
              Specify a list of attributes whose old contents are always
              logged in Modify and ModRDN requests. Usually only the
              contents of attributes that were actually modified will be
              logged; by default no old attributes are logged for ModRDN
              requests.

       logpurge <age> <interval>
              Specify the maximum age for log entries to be retained in
              the database, and how often to scan the database for old
              entries. Both the age and interval are specified as a time
              span in days, hours, minutes, and seconds. The time format
              is [ddd+]hh:mm[:ss] i.e., the days and seconds components
              are optional but hours and minutes are required. Except
              for days, which can be up to 5 digits, each numeric field
              must be exactly two digits. For example
                     logpurge 2+00:00 1+00:00
              would specify that the log database should be scanned
              every day for old entries, and entries older than two days
              should be deleted. When using a log database that supports
              ordered indexing on generalizedTime attributes, specifying
              an eq index on the reqStart attribute will greatly benefit
              the performance of the purge operation.

       logsuccess TRUE | FALSE
              If set to TRUE then log records will only be generated for
              successful requests, i.e., requests that produce a result
              code of 0 (LDAP_SUCCESS).  If FALSE, log records are
              generated for all requests whether they succeed or not.
              The default is FALSE.