[Date Prev][Date Next]
- To: "OpenLDAP Software List" <OpenLDAP-software@OpenLDAP.org>
- Subject: ldap_bind blocking
- From: "Jeremiah Martell" <firstname.lastname@example.org>
- Date: Tue, 28 Feb 2006 15:55:03 -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=rkud3qvvIUE+tmXCuo3TQj+gVd97Edz5tiGqI+pvkCEDdEAVogZYLQot6tS/7vWAee1kcfXNHIKCpl6Mt1p+LkdSxJUoS78zy7spqnkY7Y9IJNAbMCPLhmgZAl9l9CGgrZFR2xgLZd0l8ixBksOvnaxwhftOiuv0MleNzWDJTpc=
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.