https://bugs.openldap.org/show_bug.cgi?id=8847
--- Comment #37 from HoweverAT <laeufer4321(a)gmx.at> ---
(In reply to Howard Chu from comment #36)
> Since I've just been tinkering with debug output, this came to mind. With
> this patch, it would be a good idea to add the locally bound IP:port to the
> debug output somewhere, e.g. in ldap_dump_connection. Should probably use
> the recently added lutil_sockaddrstr, and that function likely should be
> moved into ldap_pvt_ instead of lutil.
Hello,
thank you for your input.
I tried to add to ldap_dump_connection( see the "from" part, which is always
printed out independet of )
e.g. Output:
** ld 0x55974c710680 Connections:
* host: localhost port: 389 (default)
* from: IP=127.0.0.1:33676
refcnt: 2 status: Connected
last used: Tue Mar 9 12:01:18 2021
** ld 0x55974c710680 Outstanding Requests:
* msgid 1, origid 1, status InProgress
outstanding referrals 0, parent count 0
ld 0x55974c710680 request count 1 (abandoned 0)
** ld 0x55974c710680 Response Queue:
Empty
ld 0x55974c710680 response count 0
I tried to add to ldap_dump_connection the "from" part which is always output
regardless of the new SOCKET_BIND_ADDRESSES option
If this ok, i could provide a patch for it tomorrow :)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6912
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs_review
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6912
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9495
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8847
--- Comment #36 from Howard Chu <hyc(a)openldap.org> ---
Since I've just been tinkering with debug output, this came to mind. With this
patch, it would be a good idea to add the locally bound IP:port to the debug
output somewhere, e.g. in ldap_dump_connection. Should probably use the
recently added lutil_sockaddrstr, and that function likely should be moved into
ldap_pvt_ instead of lutil.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8847
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
Target Milestone|2.6.0 |2.5.4
Keywords|needs_review |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8682
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|quanah(a)openldap.org |bugs(a)openldap.org
Keywords|needs_review |
Target Milestone|2.5.3 |---
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Patch welcome
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8682
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Malformatted man pages on |Malformatted man pages on
|AIX and Solaris |AIX
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8871
--- Comment #8 from hsuenju_ko(a)stratus.com <hsuenju_ko(a)stratus.com> ---
Sorry for not using the right forum. I will use a more appropriate mailing list
in the future.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8871
--- Comment #7 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
On Mon, Mar 08, 2021 at 12:30:55PM +0000, openldap-its(a)openldap.org wrote:
> --- Comment #6 from hsuenju_ko(a)stratus.com <hsuenju_ko(a)stratus.com> ---
> It seems cancel is not very useful if one cannot cancel itself and other thread
> can not cancel over same connection until the thread which performs the
> cancelled operation timeout either during the operation itself or during
> ldap_result, or doing the polling while waiting for ldap_result. Once you have
> timed out, there is no need to cancel, isn't it?
This bug tracker is not for usage questions, these should be posted to
the appropriate mailing list, usually openldap-technical.
None of what you're asking for would have worked if the thread calling
ldap_result were to release its locks anyway. You can still send a
cancel exop and you will get a response to both, if you require that the
other thread be notified immediately, you need to do that in your own
application as libldap has never had such ambitions.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8871
--- Comment #6 from hsuenju_ko(a)stratus.com <hsuenju_ko(a)stratus.com> ---
It seems cancel is not very useful if one cannot cancel itself and other thread
can not cancel over same connection until the thread which performs the
cancelled operation timeout either during the operation itself or during
ldap_result, or doing the polling while waiting for ldap_result. Once you have
timed out, there is no need to cancel, isn't it?
--
You are receiving this mail because:
You are on the CC list for the issue.