[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: write block in ber_flush under Solaris 2.6 (ITS#338)

This error is apparently caused when there is more than one outstanding
asynchronous request (bind or search) without calling ldap_result().

The documention should note that ldap_result() should be called immediately
after every asynchronous call. 

> Thanks for your report to openldap-its@OpenLDAP.org.  Your report
> has been placed into our Issue Tracking System and has been assigned
> the tracking number ITS#338.
> One of support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers.  They only work on OpenLDAP when they have spare
> time.
> You may follow the progress of this message by loading the following
> URL in a web browser:
>     http://www.OpenLDAP.org/its/index.cgi?findid=338
> Please remember to retain your issue tracking number (ITS#338)
> on any further messages you send to us regarding this message.  If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the message.
> In our experience many people ask questions that have been asked
> before.  We recommend that you review our online FAQ
> 	http://www.OpenLDAP.org/faq/
> and search archives of our many mailing lists (such as openldap-software
> and openldap-bugs). 
> 	http://www.OpenLDAP.org/lists/#archives
> --------------
> Copyright 1999 The OpenLDAP Foundation, All Rights Reserved.

Paul Amaranth        | Rochester MI, USA    
Aurora Group, Inc.   |   Systems & Software 
paul@AuroraGrp.Com   |   Unix / Windows / NT