Table
Tag | Description |
tag=107 | A result from a delete operation. |
|
|
tag=109 | A result from a moddn operation. |
|
|
tag=111 | A result from a compare operation. |
|
|
tag=115 | A search reference when the entry on which the search was performed holds a referral to the required |
| entry. Search references are expressed in terms of a referral. |
tag=120 | A result from an extended operation. |
|
|
|
|
NOTE:
tag=100 and tag=115 are not result tags as such, and so it is unlikely that they will be recorded in the access log.
5.1.2.9 Number of entries
nentries shows the number of entries, in this case nentries=0, that were found matching the LDAP client's request.
[21/Apr/2009:11:39:51
5.1.2.10 Elapsed time
etime shows the elapsed time, in this case etime=1000, or the amount of time (in seconds) that it took the Directory Server to perform the LDAP operation.
[21/Apr/2009:11:39:51
An etime value of 0 means that the operation actually took milliseconds to perform. To have microsecond resolution for this item in the access log, enter a value of 131328 (256+131072) in the
5.1.2.11 LDAP request type
The LDAP request type indicates the type of LDAP request being issued by the LDAP client. Possible values are:
SRCH | for search |
MOD | for modify |
DEL | for delete |
ADD | for add |
MODDN | for moddn |
EXT | for extended operation |
ABANDON | for abandon operation |
If the LDAP request resulted in sorting of entries, then the message SORT serialno will be recorded in the log, followed by the number of candidate entries that were sorted. For example:
[04/May/2009:15:51:46
The number enclosed in parentheses specifies the number of candidate entries that were sorted, which in this case is 1.
176 Log file reference