Thank you for the
precious hint
We passed it to the
customer.
In order to take the
right decision do you have a “not binding” indication about the 2.4.11 date. When
it is supposed to be released?
Thanks a lot
Francesco
Da: Pierangelo
Masarati [mailto:ando@sys-net.it]
Inviato: 05 February 2009 17:07
A: Francesco Grossi ITQL
Cc:
openldap-technical@openldap.org
Oggetto: Re: R: connection.c
segfault with new sasl mechanism
----- "Francesco Grossi ITQL" <f.grossi@itql.it> wrote:
>
>
Pierangelo
According to your advice
we upgraded OpenLDAP on our linux installations by moving to the latest stable
version, that is to say 2.4.11.
So far everything is
working as expected with several “long term” signon transations (such as new
pin and next token) going parallel with up to 30 straight ssh signon processes
(user + passcode).
Neither processes failed
nor fault-segmented the OpenLDAP.
We’d like to keep this
issue “open” a little bit longer just to confirm the same outcome on solaris9,
supposing the customer is available to face the production upgrade.
As soon as we have news
on it I’ll update/close the subject.
Pierangelo,
So far many many thanks for
your valuable help.
Good to hear. Since you made the effort of passing to 2.4 (which I would
have recommended anyway), please note that shortly 2.4.14 will be out. I
was just looking at the list of fixes since 2.4.13 (and since 2.4.11), so
you'll probably want to move to 2.4.14 before your project is over. In
any case, feel free to report any further issue you may encounter. I
recommend running the server under valgrind anyway, it could help highlighting
memory issues like the one you were experiencing.
Cheers, p.
Ing.
Pierangelo Masarati
OpenLDAP Core Team
SysNet
s.r.l.
Via Dossi, 8 - 27100 Pavia - ITALIA
|
|
|
|
Office: |
+39 02 23998309 |
|
Mobile: |
+39 333 4963172 |
|
Fax: |
+39 0382 476497 |
|
Email: |
|
|
|
|