Search Scope - Red Hat DIRECTORY SERVER 7.1 Configuration

Access Log Content
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
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,
beforeCount= 0
afterCount= 5
value= 0210
and the second part,
targetPosition= 10
contentCount= 5397
(resultCode)= (0)

Search Scope

The entry
value of
= base search
0
= one-level search
1
= subtree search
2
For more information about search scopes, see "Using ldapsearch" in Appendix
B, "Finding Directory Entries," in the Red Hat Directory Server Administrator's
Guide.
216 Red Hat Directory Server Configuration, Command, and File Reference • May 2005
10:5397 (0)
defines the scope of the search performed, and
scope=n
, , or .
0 1 2
afterCount value.
: :
, is the VLV request information:
0:5:0210
, is the VLV response information:
can have a
n