1 .\" Copyright 2004-2011 The OpenLDAP Foundation All Rights Reserved.
2 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
3 .TH SLAPO_LASTMOD 5 "RELEASEDATE" "OpenLDAP LDVERSION"
5 slapo-lastmod \- Last Modification overlay
12 overlay creates a service entry rooted at the suffix of the database
13 it's stacked onto, which holds the DN, the modification type,
14 the modifiersName and the modifyTimestamp of the last write operation
15 performed on that database.
16 The lastmod overlay cannot be used when the "lastmod" feature
17 is disabled, i.e. "lastmod off" is used.
19 All operations targeted at the DN of the lastmod entry are rejected,
20 except reads, i.e. searches with
23 Regular operations are ignored, unless they result in writing; then,
24 in case of success, the lastmod entry is updated accordingly,
30 configuration options apply to the lastmod overlay. They must appear
35 .B lastmod-rdnvalue <RDN value>
36 Specify the value of the RDN used for the service entry. By default
40 .B lastmod-enabled {yes|no}
41 Specify whether the overlay must be enabled or not at startup.
42 By default, the overlay is enabled; however, by changing the boolean
43 value of the attribute
45 one can affect the status of the overlay.
46 This is useful, for instance, to inhibit the overlay from keeping track
47 of large bulk loads or deletions.
52 overlay depends on the
54 objectClass. The definition of that class is as follows:
57 ( 1.3.6.1.4.1.4203.666.3.13 "
59 DESC 'OpenLDAP per-database last modification monitoring'
62 MUST ( cn $ lastmodDN $ lastmodType )
63 MAY ( description $ seeAlso ) )
68 Each one of the sections below details the meaning and use of a particular
72 Most of the attributes that are specific to the lastmod objectClass are
73 operational, since they can logically be altered only by the DSA.
74 The most notable exception is the
76 attributeType, which can be altered via protocol to change the status
82 This attribute contains a boolean flag that determines the status
83 of the overlay. It can be altered via protocol by issuing a modify
84 operation that replaces the value of the attribute.
87 ( 1.3.6.1.4.1.4203.666.1.30
89 DESC 'Lastmod overlay state'
90 SYNTAX 1.3.6.1.4.1.1466.115.121.1.7
95 .SH OPERATIONAL ATTRIBUTES
97 Each one of the sections below details the meaning and use of a particular
101 Most of the attributes that are specific to the lastmod objectClass are
102 operational, since they can logically be altered only by the DSA.
107 This attribute contains the distinguished name of the entry
108 that was last modified within the naming context of a database.
111 ( 1.3.6.1.4.1.4203.666.1.28
113 DESC 'DN of last modification'
114 EQUALITY distinguishedNameMatch
115 SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
117 USAGE directoryOperation )
122 This attribute contains the type of the modification that occurred
123 to the last modified entry. Legal values are
131 The latter should only be used as a fall-thru in case of unhandled
132 request types that are considered equivalent to a write operation.
135 ( 1.3.6.1.4.1.4203.666.1.29
137 DESC 'Type of last modification'
138 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
139 EQUALITY caseIgnoreMatch
142 USAGE directoryOperation )
151 suffix dc=example,dc=com
154 lastmod-rdnvalue "Last Modification"
162 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
166 It is unclear whether this overlay can safely interoperate
168 If the underlying backend does not implement entry_get/entry_release
169 handlers, modrdn update can become tricky.
170 The code needs some cleanup and more consistent error handling.
171 So far, the OIDs for the schema haven't been assigned yet.
175 This module was written in 2004 by Pierangelo Masarati in fulfillment
176 of requirements from SysNet s.n.c.; this man page has been copied
178 .BR slapo-ppolicy (5),
179 and most of the overlays ever written are copied from Howard Chu's
183 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
185 is derived from University of Michigan LDAP 3.3 Release.