Christopher Paul wrote:
> On 4/17/2024 11:24 PM, Howard Chu wrote:
>> timeout has nothing to do with the duration of an operation.
>=20
> I'm confused then. Manual page ldap.conf(5) states:
>=20
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 TIMEOUT <integer>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Specifies a timeout (in seconds) after which calls to synchronous =
LDAP APIs will abort if no response is received.=C2=A0 Also used for any
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 ldap_result(3) calls where a NULL timeout parameter is supplied.
>=20
> The duration of an operation is the call to the LDAP API plus the time =
it takes for the response/result, no? What am I missing here?

The manpage language is precise. Your paraphrase is not.

An LDAP operation may have more than one response. Search operations ofte=
n do, extended ops may as well.
The timeout is waiting for any response, not just the operation result.

--=20
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/