SLAPOLASTMOD(5) SLAPOLASTMOD(5)

NAME
       slapo-lastmod - Last Modification overlay

SYNOPSIS
       /etc/openldap/slapd.conf

DESCRIPTION
       The llaassttmmoodd overlay creates a service entry rooted at the suffix of the
       database it's stacked onto, which holds the DN, the modification  type,
       the  modifiersName  and the modifyTimestamp of the last write operation
       performed on that database.  The lastmod overlay cannot  be  used  when
       the "lastmod" feature is disabled, i.e. "lastmod off" is used.

       All  operations  targeted  at the DN of the lastmod entry are rejected,
       except reads, i.e. searches with bbaassee scope.   Regular  operations  are
       ignored,  unless  they result in writing; then, in case of success, the
       lastmod entry is updated accordingly, if possible.


CCOONNFFIIGGUURRAATTIIOONN
       These ssllaappdd..ccoonnff configuration options apply to  the  lastmod  overlay.
       They must appear after the oovveerrllaayy directive.

       llaassttmmoodd-rrddnnvvaalluuee <>
              Specify  the  value  of  the RDN used for the service entry.  By
              default Lastmod is used.

       llaassttmmoodd-eennaabblleedd {{yyeess||nnoo}}
              Specify whether the overlay must be enabled or not  at  startup.
              By  default,  the  overlay  is enabled; however, by changing the
              boolean value of the attribute lastmodEnabled,  one  can  affect
              the  status  of  the  overlay.  This is useful, for instance, to
              inhibit the overlay from keeping track of large  bulk  loads  or
              deletions.


OOBBJJEECCTT CCLLAASSSS
       The llaassttmmoodd overlay depends on the llaassttmmoodd objectClass.  The definition
       of that class is as follows:

           ( 1.3.6.1.4.1.4203.666.3.13 "
               NAME 'lastmod'
               DESC 'OpenLDAP per-database last modification monitoring'
               STRUCTURAL
               SUP top
               MUST ( cn $ lastmodDN $ lastmodType )
               MAY ( description $ seeAlso ) )


AATTTTRRIIBBUUTTEESS
       Each one of the sections below details the meaning and use of a partic-
       ular  attribute  of  this  llaassttmmoodd objectClass.  Most of the attributes
       that are specific to the lastmod  objectClass  are  operational,  since
       they can logically be altered only by the DSA.  The most notable excep-
       tion is the lastmodEnabled attributeType, which can be altered via pro-
       tocol to change the status of the overlay.


       llaassttmmooddEEnnaabblleedd

       This  attribute  contains  a boolean flag that determines the status of
       the overlay.  It can be altered via protocol by issuing a modify opera-
       tion that replaces the value of the attribute.

           (  1.3.6.1.4.1.4203.666.1.30
              NAME 'lastmodEnabled'
              DESC 'Lastmod overlay state'
              SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
              EQUALITY booleanMatch
              SINGLE-VALUE )


OOPPEERRAATTIIOONNAALL AATTTTRRIIBBUUTTEESS
       Each one of the sections below details the meaning and use of a partic-
       ular attribute of this llaassttmmoodd objectClass.   Most  of  the  attributes
       that  are  specific  to  the lastmod objectClass are operational, since
       they can logically be altered only by the DSA.


       llaassttmmooddDDNN

       This attribute contains the distinguished name of the  entry  that  was
       last modified within the naming context of a database.

           (  1.3.6.1.4.1.4203.666.1.28
              NAME 'lastmodDN'
              DESC 'DN of last modification'
              EQUALITY distinguishedNameMatch
              SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
              NO-USER-MODIFICATION
              USAGE directoryOperation )

       llaassttmmooddTTyyppee

       This  attribute  contains the type of the modification that occurred to
       the last modified entry.  Legal values are aadddd, ddeelleettee,  eexxoopp,  mmooddiiffyy,
       mmooddrrddnn  and  uunnkknnoowwnn.  The latter should only be used as a fall-thru in
       case of unhandled request types that are  considered  equivalent  to  a
       write operation.

           (  1.3.6.1.4.1.4203.666.1.29
              NAME 'lastmodType'
              DESC 'Type of last modification'
              SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
              EQUALITY caseIgnoreMatch
              SINGLE-VALUE
              NO-USER-MODIFICATION
              USAGE directoryOperation )



EEXXAAMMPPLLEESS
              database    bdb
              suffix      dc=example,dc=com
              overlay     lastmod
              lastmod-rdnvalue "Last Modification"


SEE ALSO
       llddaapp(3), ssllaappdd..ccoonnff(5),

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



BUGS
       It  is  unclear whether this overlay can safely interoperate with other
       overlays.    If   the   underlying   backend   does    not    implement
       entryget/entryrelease handlers, modrdn update can become tricky.  The
       code needs some cleanup and more consistent error  handling.   So  far,
       the OIDs for the schema haven't been assigned yet.


AACCKKNNOOWWLLEEDDGGEEMMEENNTTSS
       This  module  was written in 2004 by Pierangelo Masarati in fulfillment
       of requirements from SysNet s.n.c.; this man page has been copied  from
       ssllaappoo-ppppoolliiccyy(5), and most of the overlays ever written are copied from
       Howard Chu's first overlays.

       OOppeennLLDDAAPP  is  developed  and  maintained  by   The   OpenLDAP   Project
       (http://www.openldap.org/).   OOppeennLLDDAAPP  is  derived  from University of
       Michigan LDAP 3.3 Release.



OpenLDAP 2.3.27                   2006/08/19                  SLAPOLASTMOD(5)