Access Log Content
216 Red Hat Directory Server Configuration, Command, and File Reference • May 2005
beforeCount:afterCount:index:contentCount
and ResponseInformation
is of the form:
targetPosition:contentCount (resultCode)
If the client uses a position-by-value VLV request, the format for the first part, the
request information would be beforeCount
:
afterCount
:
value.
The example below shows VLV-specific entries in bold:
[07/May/2005:11:43:29 -0700] conn=877 op=8530 SRCH
base="(ou=People)" scope=2 filter="(uid=*)"
[07/May/2005:11:43:29 -0700] conn=877 op=8530 SORT uid
[07/May/2005:11:43:29 -0700] conn=877 op=8530 VLV 0:5:0210
10:5397 (0)
[07/May/2005:11:43:29 -0700] conn=877 op=8530 RESULT err=0
tag=101 nentries=1 etime=0
In the above example, the first part,
0:5:0210
, is the VLV request information:
beforeCount= 0
afterCount= 5
value= 0210
and the second part,
10:5397 (0)
, is the VLV response information:
targetPosition= 10
contentCount= 5397
(resultCode)= (0)
Search Scope
The entry
scope=n
defines the scope of the search performed, and
n
can have a
value of
0
,
1
, or
2
.
0
= base search
1
= one-level search
2
= subtree search
For more information about search scopes, see “Using ldapsearch” in Appendix
B, “Finding Directory Entries,” in the Red Hat Directory Server Administrator’s
Guide.
To Next Page
Loading...
