On 4/18/2024 11:30 AM, Howard Chu wrote:
An LDAP operation may have more than one response. Search operations often do,
extended ops may as well.
The timeout is waiting for any response, not just the operation result.
Ah, that makes sense now. Thanks, Howard!
--
Chris Paul | Rex Consulting
Christopher Paul wrote:
> On 4/17/2024 11:24 PM, Howard Chu wrote:
>> timeout has nothing to do with the duration of an operation.
>
> I'm confused then. Manual page ldap.conf(5) states:
>
> TIMEOUT
> Specifies a timeout (in seconds) after which calls to
> synchronous LDAP
On 4/17/2024 11:24 PM, Howard Chu wrote:
timeout has nothing to do with the duration of an operation.
I'm confused then. Manual page ldap.conf(5) states:
TIMEOUT
Specifies a timeout (in seconds) after which calls to
synchronous LDAP APIs will abort if no response is
Christopher Paul wrote:
> Concerning the "timeout" parameter, the ideal range might be between 60 to
> 120 seconds, to handle operations exceeding a minute, but again, kicking in
> retry
> logic if they exceed two minutes. I admit that my stance on the "timeout"
> setting is tentative, given
--On Monday, April 8, 2024 3:08 PM +0900 Christopher Paul
wrote:
Hello OpenLDAP-technical list,
I'm curious about community perspectives on a specific LDAP replication
timeout and network-timeout settings:
Setting "timeout=0" or "network-timeout=0" within a syncrepl/olcSyncrepl
