Red Hat 8.1 User Manual download pdf (Page 238)

Chapter 5. Log File Reference

224

• 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 -0700] conn=114 op=68 SORT serialno (1)

The number enclosed in parentheses specifies the number of candidate entries that were sorted,

which in this case is 1.

LDAP Response Type

The LDAP response type indicates the LDAP response being issued by the LDAP client. There are

three possible values:

• RESULT

• ENTRY

• REFERRAL, an LDAP referral or search reference

Unindexed Search Indicator

The unindexed search indicator, notes=U, indicates that the search performed was unindexed,

which means that the database itself had to be directly searched instead of the index file. Unindexed

searches occur in three scenarios:

• When the nsslapd-idlistscanlimit was reached within the index file used for the search.

• When no index file existed.

• When the index file was not configured in the way required by the search.

NOTE

An unindexed search indicator is often accompanied by a large etime value, as

unindexed searches are generally more time consuming.

VLV-Related Entries

When a search involves virtual list views (VLVs), appropriate entries are logged in the access log file.

Similar to the other entries, VLV-specific entries show the request and response information side by

side:

VLV RequestInformation ResponseInformation

RequestInformation has the following form:

beforeCount:afterCount:index:contentCount

If the client uses a position-by-value VLV request, the format for the first part, the request information

would be beforeCount: afterCount: value.

ResponseInformation has the following form:

1 2 ... 233 234 235 236 237 238 239 240 241 242 243 ... 373 374

No comments

Red Hat 8.1 User Manual Page 238