Hi,
you were indeed right. It is a problem with the version of libldap and the use
of openssl.
I first tried to build upstream ldapvi on etch using openssl and the default
libldap2-dev (2.1.30-13.3) which didn't solve the problem. I then built ldap
libraries from the openldap2.3_2.3.30.orig.tar.gz source package (from which
ldapsearch is coming) and linked ldapvi with openssl and these ldap (2.3)
libraries:
ldd ldapvi:
linux-gate.so.1 => (0xffffe000)
libcrypt.so.1 => /lib/tls/i686/cmov/libcrypt.so.1 (0xb7f13000)
libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0xb7ed4000)
libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7d9a000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7d08000)
libreadline.so.5 => /lib/libreadline.so.5 (0xb7cd8000)
libpopt.so.0 => /lib/libpopt.so.0 (0xb7ccf000)
libncurses.so.5 => /lib/libncurses.so.5 (0xb7c8e000)
libldap-2.3.so.0 => /usr/lib/libldap-2.3.so.0 (0xb7c58000)
<<<<<<<<<
liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0xb7c4c000)
libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2 (0xb7c39000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7b08000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7b03000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7aef000)
librt.so.1 => /lib/tls/i686/cmov/librt.so.1 (0xb7ae6000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb7ad0000)
/lib/ld-linux.so.2 (0xb7f5d000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7abe000)
As one can see this ldapvi uses now the same libldap as ldapsearch and the
problem goes away!
I guess, ldapvi would have to be built with a more recent version of the ldap
libraries.
Kind regards,
Ch. Scheurer
On Fri, Apr 27, 2007 at 12:58:32PM +0200, David Lichteblau wrote:
> Hi,
>
> Quoting Christoph Scheurer ([EMAIL PROTECTED]):
> > For comparison
> > ldapsearch -ZZ -Y GSSAPI '(uid=XXXX)'
> > which, as I understand, does exactly the same as ldapvi until the editor is
> > opened, yields a search result immediately and does not use a noticable
> > amount
> > of CPU on the exact same client machine.
>
> well, there's a difference between how ldapsearch and ldapvi are built
> by Debian.
>
> ldapsearch uses current libldap and OpenSSL.
> ldapvi uses an ancient libldap and GnuTLS. (In Debian only.)
>
> - Can you try building current ldapvi using upstream sources rather
> than the debian package to confirm that the issues are not due to
> the Debian-specific build changes?
>
> Upstream ldapvi will use OpenSSL by default.
>
>
> - When building on Debian normally, you will still end up linking
> ldapvi against the ancient libldap, though.
>
> So if upstream ldapvi using Debian's old libldap does not help,
> please try upstream ldapvi using upstream libldap.
>
>
> Thanks,
> David
>
--
Christoph Scheurer GnuPG key Id: 0x6128C6B6
contact: http://www.theo.chemie.tu-muenchen.de/homepages/scheurer/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
