HP-UX Directory Server 8.1 configuration, command, and file reference

1
For one-level search
2
For subtree search
For more information about search scopes, see "Using ldapsearch" in Appendix B, "Finding
Directory Entries", in the HP-UX Directory Server administrator guide. XXX
5.1.2.16 Extended operation OID
An extended operation OID, in this case either EXT oid="2.16.840.1.113730.3.5.3" or
EXT oid="2.16.840.1.113730.3.5.5", provides the OID of the extended operation being
performed. The following table provides a partial list of LDAPv3 extended operations and their
OIDs supported in Directory Server.
Table 5-2 LDAPv3 extended operations supported by Directory Server
OIDDescriptionExtended operation name
2.16.840.1.113730.3.5.3Sent by a replication initiator to indicate that a
replication session is requested.
Directory Server Start
Replication Request
2.16.840.1.113730.3.5.4Sent by a replication responder in response to a
Start Replication Request Extended Operation
or an End Replication Request Extended
Operation.
Directory Server Replication
Response
2.16.840.1.113730.3.5.5Sent to indicate that a replication session is to
be terminated.
Directory Server End Replication
Request
2.16.840.1.113730.3.5.6Carries an entry, along with its state information
(csn and UniqueIdentifier) and is used to
perform a replica initialization.
Directory Server Replication
Entry Request
2.16.840.1.113730.3.5.7Sent by the client to request a bulk import
together with the suffix being imported to and
sent by the server to indicate that the bulk
import may begin.
Directory Server Bulk Import
Start
2.16.840.1.113730.3.5.8Sent by the client to signal the end of a bulk
import and sent by the server to acknowledge
it.
Directory Server Bulk Import
Finished
5.1.2.17 Change sequence number
The change sequence number, in this case csn=3b4c8cfb000000030000, is the replication
change sequence number, indicating that replication is enabled on this particular naming context.
5.1.2.18 Abandon message
The abandon message indicates that an operation has been aborted.
[21/Apr/2009:11:39:52 -0700] conn=12 op=2 ABANDON targetop=1 msgid=2 nentries=0 etime=0
Where:
nentries=0
Indicates the number of entries sent before the operation was aborted.
etime=0
Iindicates how much time (in seconds) had elapsed.
targetop=1
Corresponds to an operation value from a previously initiated operation (that
appears earlier in the access log).
There are two possible log ABANDON messages, depending on whether the message ID succeeds
in locating which operation was to be aborted. If the message ID succeeds in locating the operation
(the targetop) then the log will read as above. However, if the message ID does not succeed
in locating the operation or if the operation had already finished before the ABANDON request
was sent, then the log will read as follows:
[21/Apr/2009:11:39:52 -0700] conn=12 op=2 ABANDON targetop=NOTFOUND msgid=2
178 Log file reference