RE: Who is using python-ldap with Python 1.5.x and 2.0-2.2?

Hi Michael, Thank you for all your hard work! We are using python2.4.4, but only because of other software that is tied to it and the lack of available time to upgrade. Ron Teitelbaum > -Original Message- > From: [EMAIL PROTECTED] [mailto:python-ldap- > [EMAIL PROTECTED] On

RE: Problem on add

Hi Michele, Have a look at this http://www.grotan.com/ldap/python-ldap-samples.html I thought it was pretty helpful. It's easier to build the ldif using the modlist. Ron > -Original Message- > From: [EMAIL PROTECTED] [mailto:python-ldap- > [EMAIL PROTECTED] On Behalf Of Michele Petrazzo

RE: module ldap : no module named .py

Hi David, I had this happen before because I tried to do this: Import aModuleName.py I don't see that mistake in your code though, but maybe something you are calling is doing that. You need to leave off the .py when doing import. Hope that helps, Ron _ From: [EMAI

RE: Killed Python2.4

D] > Cc: python-ldap-dev@lists.sourceforge.net > Subject: Re: Killed Python2.4 > > Ron Teitelbaum wrote: > > ldd libldap.so > > linux-gate.so.1 => (0x002d7000) > > liblber-2.3.so.0 => /usr/lib/liblber-2.3.so.0 (0x00176000) > > libr

RE: Killed Python2.4

dde000) libsepol.so.1 => /lib/libsepol.so.1 (0x00d96000) It looks quite different from your version. Thanks, Ron > -----Original Message- > From: Michael Ströder > > Ron Teitelbaum wrote: > > > > I know you mentioned that I should send you more info if I get an &

RE: Killed Python2.4

libselinux.so.1 => /lib/libselinux.so.1 (0x002af000) libsepol.so.1 => /lib/libsepol.so.1 (0x004c1000) Thanks, Ron > -Original Message----- > From: Michael Ströder [mailto:[EMAIL PROTECTED] > > Ron Teitelbaum wrote: > > ldd libldap.so > > linux-

Killed Python2.4

Hi Michael, I know you mentioned that I should send you more info if I get an exception. I got a SERVER_DOWN and then retried the call manually and blew up python2.4 This is CentOS 5, python2.4.4, python-ldap 2.3.4 File "/usr/lib/python2.4/site-packages/ldap/ldapobject.py", line 507, in search

RE: One result call per record

--Original Message- > From: Michael Ströder > > Ron Teitelbaum wrote: > > While polling it appears that we have to call result for every record > that > > is waiting to be read. Since we added a 250 millisecond delay between > calls > > larger queries are tak

One result call per record

Hi all, We are experiencing something pretty odd. CentOS 5 python2.4.4 python-ldap 2.3.4 While polling it appears that we have to call result for every record that is waiting to be read. Since we added a 250 millisecond delay between calls larger queries are taking a really long time. def se

RE: Leaving a connection open

> From: Michael Ströder > > Ron Teitelbaum wrote: > > I have a few questions about leaving a bound connection open for sharing > > (python 2.4.4, python-ldap 2.2.1 - openldap 2.3-2.3.30 on Ubuntu 7.04). > > > > I'm using Async messages is there any benefit t

Leaving a connection open

died so that I can reconnect a shared connection if the connection dropped off? I tried unbind and whoami_s but got a very nasty memory error after a very long delay. Thanks for your help! Ron Teitelbaum - Check out th

CLOSE_WAIT sessions (was: Too many established connections)

Hi Michael, > -Original Message- > From: Michael Ströder > > Ron Teitelbaum wrote: > > > > I'm running into a problem with python open ldap connections. > > Do you mean python-ldap connections o

Too many established connections

et a significant number of can not connect problems that I handle with a retry. The server died the first time we tried to put a significant load on it. Does anyone have suggestions for fixing this problem or figuring out what is leaving connections open

Commiting multiple objects

Hello, I have to commit multiple objects. Can I use the modlist to store and commit multiple objects at once. If so is it possible to order the objects so that they commit a subtree before the leaves? Thanks for your help! Ron Teitelbaum

RE: Exception info: Already Exists on New Add

Hi Michael, Thank you very much for your help. I will look at the exception handler and ReconnectLDAPObject. I see the multiple calls to add_ext and the different results, so you are right, it's me! Thanks! Ron > -Original Message- > From: Michael Ströder > > Ron

Exception info: Already Exists on New Add

nyway. I'm running on Ubuntu 7.04 (VMWare). Python2.4. Python-ldap 2.2.1 I've attached the trace file. Any idea why I would get this result? If the record was inserted then why am I getting this Can't contact error, and if it didn't insert the record because it couldn&#x