https://bugs.openldap.org/show_bug.cgi?id=8577
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 7a4e70f3
by Howard Chu at 2021-03-21T17:20:05+00:00
ITS#8577 don't allow setting logDB to current DB
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8726
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• cbb6441c
by Howard Chu at 2021-03-21T16:36:30+00:00
ITS#8726 check newly registered loglevels immediately
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7295
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ, reviewed |
--- Comment #4 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• bb6844e2
by Howard Chu at 2021-03-21T15:26:57+00:00
ITS#7295 don't init TLS threads by default
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8246
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ, reviewed |
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• 7ff1f42f
by Howard Chu at 2021-03-21T14:58:22+00:00
ITS#8246 frontend and config DBs are unique
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9016
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• cf67fc22
by Ondřej Kuzník at 2021-03-19T12:48:09+00:00
ITS#9016 Do not forget to close directory handle
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8589
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
fixed in master
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9152
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Howard Chu <hyc(a)openldap.org> ---
Fixed in master.
Note that in this case, the overlay will never auto-install its own server
cert, you'll have to explicitly provide it later.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8577
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
fixed in master
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8726
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
--- Comment #3 from Howard Chu <hyc(a)openldap.org> ---
fixed in master
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8545
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
(In reply to shalopo(a)gmail.com from comment #0)
> Full_Name: Shahar Lupu
> Version: 2.4.44
> OS: Ubuntu
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (81.218.29.26)
>
>
> When calling ldap_result with a timeout={0,0} (polling), it returns
> LDAP_TIMEOUT
> even though there are available messages in the socket.
> This occurs when calling ldap_results with all=true and a multi-message
> response
> has arrived. In this case, if the client has already received on the socket
> every message for the response, it is desirable that all the messages are
> collected within this ldap_result call. Instead of only polling for the
> specified timeout, ldap_result applies the timeout (zero when polling) on the
> wait4msg loop. Consequently, ldap_result returns LDAP_TIMEOUT after the first
> message if the response is composed of more than one message.
> While it may be a good idea to apply a timeout for the wai4msg loop (rather
> than
> only the polling on the socket), it is undesirable in some cases and should
> at
> least be configurable. Or perhaps timeout=polling should never be applied on
> the
> wait4msg loop.
None of this will make any difference. In try_read1msg, there is a check
to see if the socket is still readable at the end, in which case it will
loop back and read the next message. As such, when it returns to wait4msg,
all readable messages have already been processed. So even if it returns
LDAP_TIMEOUT, it returns all available messages. If it only returns one
message, that means no others were available.
--
You are receiving this mail because:
You are on the CC list for the issue.