[Date Prev][Date Next]
ASYNC call blocking
- To: "OpenLDAP Software List" <OpenLDAP-software@OpenLDAP.org>
- Subject: ASYNC call blocking
- From: "Jeremiah Martell" <firstname.lastname@example.org>
- Date: Mon, 6 Mar 2006 14:41:20 -0500
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=LzPeES8VAb/vXi2lQN6ilV/2l8LPwLFaE3DXGrCX5o+iToa1f+vxdXk1NRFi4TlRZw5dt0LPOkphS28aisn+ST7zqwdiszA9cmaexmapSwCqoYO0n49UDM78iSUrGYqqfWtpM9tf/dZVKO3vE7OqkLVvSuLDjxycLMnd5NqInlE=
I posted a message a week ago about the ASYNC ldap_bind call blocking.
ldap_bind is supposed to be ASYNC and not block, and ldap_bind_s is
supposed to be SYNC and block. But both ldap_bind_s AND ldap_bind is
ldap_bind will block with a bogus IP or with no active internet connection.
Has anybody successfully used ldap_bind? Is this a known bug? Is there
a workaround? Has it been fixed since 2.2.17?
It seems that a call to ldap_bind blocks. I expected ldap_bind to
always immediately return the id. However, if I unplug the ethernet
cable from my computer and run my application, the call to ldap_bind
blocks. While my application is sitting there blocked if I plug the
ethernet plug back in, the call returns the id and then behaves as
I also noticed that ldap_bind blocks if you're attempting to
connect to a bogus IP address.
Is there something else I need to do so that ldap_bind never blocks?
I'm using openldap-2.2.17.