python-ldap-dev — discussion among developers

=?ISO-8859-1?Q?R=E9p.=20:=20Re:=20NDS=20library=20linking?=

[Olivier D. <OD...@is...>]

Thank you for this information, Tim.

My problem is :

When binding to NDS with simple_bind_s() function, it works fine with a C =
program calling the Novell LDAP library, but it doesn't work with a python =
script using python-LDAP : the program is frozen.

>>> Timothy Wilson <wi...@vi...> 05/09/01 17:31:52 >>>
On Wed, 5 Sep 2001, Olivier Dewit wrote:

> I would like to use python-ldap with NDS. I didn't find any documentation=
 on it. Is it possible ? Is there anybody who could explain to me step by =
step how to compile and link python-ldap with the Novell library?

I don't know if you want to do anything fancy, but the simple tests I've =
run
worked perfectly with the regular ldap modules. I'm able to query NDS with
no problem. NDS speaks LDAP fluently. :-)

-Tim

--
Tim Wilson      |   Visit Sibley online:   | Check out:
Henry Sibley HS |  http://www.isd197.org   | http://www.zope.com=20
W. St. Paul, MN |                          | http://slashdot.org=20
wi...@vi... |  <dtml-var pithy_quote>  | http://linux.com=20

Re: NDS library linking

[Timothy W. <wi...@vi...>]

On Wed, 5 Sep 2001, Olivier Dewit wrote:

> I would like to use python-ldap with NDS. I didn't find any documentation on it. Is it possible ? Is there anybody who could explain to me step by step how to compile and link python-ldap with the Novell library?

I don't know if you want to do anything fancy, but the simple tests I've run
worked perfectly with the regular ldap modules. I'm able to query NDS with
no problem. NDS speaks LDAP fluently. :-)

-Tim

--
Tim Wilson      |   Visit Sibley online:   | Check out:
Henry Sibley HS |  http://www.isd197.org   | http://www.zope.com
W. St. Paul, MN |                          | http://slashdot.org
wi...@vi... |  <dtml-var pithy_quote>  | http://linux.com

NDS library linking

[Olivier D. <OD...@is...>]

Hello,

I would like to use python-ldap with NDS. I didn't find any documentation =
on it. Is it possible ? Is there anybody who could explain to me step by =
step how to compile and link python-ldap with the Novell library?

The Linux Novell library is available at http://developer.novell.com/ndk/cl=
daplin.htm. The library files are not the same that OpenLDAP ones.

Thank you for your help,

Olivier

make error

[Kaeidinejad, S. <Sha...@dg...>]

hi,
i try to compile python-ldap-1.10alpha3 for python-2.1.1 but i got this
error by the make.

ld: fatal: relocations remain against allocatable but non-writable sections
collect2: ld returned 1 exit status
make: *** [ldapmodule.so] Error 1

can you help me?

thank

shahram

Re: Tagging the CVS archive

[Konstantin C. <Kon...@da...>]

Hi Michael and All,

Michael Ströder wrote:

> sorry for answering that late.
>

No worries, same problem here: I have been too busy last couple of months...

I have just tagged the repository with the OPENLDAP_1_BRANCH tag. Everything
seems to be OK, at least I can see and choose that tag in the Sourceforge
web-to-CVS gateway.
Anybody willing to roll out the release for OpenLDAPv1?
I'm going to add OpenLDAPv2 patches soon. The first goal is to handle
referrals, the second one is a new version of the rebind_proc callback. Note
that in the C API, OpenLDAPv1 rebind_proc is incompatible with OpenLDAPv2. I do
not see the way of providing compatibility between them, because the callback
mechanism itself has changed completely. So I think we need a change in
python-ldap API as well. Do you have any suggestions about it?

Regards,
    Konstantin.

>
> Konstantin Chuguev wrote:
> >
> > I think there's no point to postpone introduction of the OpenLDAPv1 branch
> > in the CVS.
>
> Agreed.
>
> > I can do that, I just need an approval from one of the project
> > admins.
>
> Hmm, not sure if I'm a project admin. Well, I'm listed there...
>
> > The proposed name is openldap_1_branch. It will be made on both
> > python-ldap and htdocs directories.
>
> Please use capital letters OPENLDAP_1_BRANCH but not on the htdocs/
> directory. Go for it.
>
> > A small question: there are HTML links to files in htdocs/doc/ directory
> > from htdocs/docs.shtml file, while there's no such directory. Why?
>
> The directory htdocs/ is solely dedicated to manage the web pages on
> http://python-ldap.sf.net. Leave that out. It's not part of a
> release tar-ball.
>
> Ciao, Michael.

--
         * *       Konstantin Chuguev           Francis House
      *      *     Application Engineer         112 Hills Road
    *              Tel: +44 1223 302992         Cambridge CB2 1PQ
D  A  N  T  E      WWW: http://www.dante.net    United Kingdom

Handling of Unicode objects (was: start tls)

[Michael <mi...@st...>]

Steffen Ries wrote:
> 
> attached is a small (experimental) patch, which enables
> 'start_tls_s()' in python-ldap. The patch requires OpenLDAP 2.0.x (I
> tested it only against 2.0.11 on Redhat 6.2).
> 
> I included Konstanin's patches and the memory leak fixes and have run
> the diff against the current CVS version. David's CIDict patches
> are not included, so I disabled CIDict to get it running with
> python2.1.

BTW: It seems that in opposite to the former python-ldap Unicode
strings are accepted by e.g. the modify() call when these patches
are applied.

In the beginning I considered this also to be a good idea. But now I
think this is flawed since we don't have a way to define how the
Unicode objects are encoded to strings. Note that this would require
knowledge about the syntax of a certain attribute type => the LDAP
application should handle that.

If you examine RFC2251 (Lightweight Directory Access Protocol (v3))
you will notice that all transmitted strings are encoded as OCTET
STRING no matter what attribute value they contain. Therefore the
best bet seems to me to solely accept type('') at python-ldap's API
level for attribute values. The calling application should be
responsible for handle Unicode objects.

Ciao, Michael.

Re: start tls

[Michael <mi...@st...>]

Steffen Ries wrote:
> 
> Can you run python inside gdb to get a traceback? Or give me more
> details how you got the segfaults?

I tried it but I'm a complete newbie regarding gdb. The seg faults
seem to happen at various places. Maybe it has to do with threading
problems? web2ldap can run threaded or "single-threaded". In
latter mode only a clean-up thread is running besides the main thread.
In multi-threaded mode each HTTP request is handled by an own
handler thread (my wrapper module ldapthreadlock is used in this
case to avoid re-entrant calls into the LDAP libs).

I've started the web2ldap stand-alone demon non-detached and
attached gdb to it by issuing

$ sbin/web2ldap.py -d off -t off
$ gdb /usr/bin/python [web2ldap's PID]
[..
  snipped a lot of gdb-output related to shared lib loading
..]
0x4012b772 in __libc_accept () from /lib/libc.so.6
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1026 (LWP 2840)]
0x4002da78 in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x4002da78 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x400d223b in free () from /lib/libc.so.6
#2  0x4038c47c in dealloc (self=0x4055ea10) at Modules/LDAPObject.c:46
#3  0x808ea38 in dict_dealloc (mp=0x405d517c) at Objects/dictobject.c:629
#4  0x807fad9 in instance_dealloc (inst=0x405d4ccc) at Objects/classobject.c:583
#5  0x805772d in eval_code2 (co=0x4018c120, globals=0x40190b3c, locals=0x0, 
    args=0x819e0b0, argcount=1, kws=0x819e0b4, kwcount=0, defs=0x0, defcount=0, 
    closure=0x0) at Python/ceval.c:1673
#6  0x80598fd in fast_function (func=0x401f309c, pp_stack=0xbf7ff9dc, n=1, na=1, 
    nk=0) at Python/ceval.c:3022
#7  0x8057f85 in eval_code2 (co=0x401a54a0, globals=0x401a735c, locals=0x0, 
    args=0x4051a438, argcount=1, kws=0x0, kwcount=0, defs=0x0, defcount=0, 
    closure=0x0) at Python/ceval.c:1972
#8  0x80597e7 in call_eval_code2 (func=0x401af72c, arg=0x4051a42c, kw=0x0)
    at Python/ceval.c:2966
#9  0x80593e2 in call_object (func=0x401af72c, arg=0x4051a42c, kw=0x0)
    at Python/ceval.c:2805
#10 0x805969c in call_method (func=0x401af72c, arg=0x40177074, kw=0x0)
    at Python/ceval.c:2923
#11 0x80593c6 in call_object (func=0x4055f98c, arg=0x40177074, kw=0x0)
    at Python/ceval.c:2803
#12 0x80592ae in PyEval_CallObjectWithKeywords (func=0x4055f98c, arg=0x40177074, 
    kw=0x0) at Python/ceval.c:2740
#13 0x8072d19 in t_bootstrap (boot_raw=0x8165fc8) at ./Modules/threadmodule.c:190
#14 0x4002cca3 in pthread_start_thread () from /lib/libpthread.so.0
(gdb) 

Ciao, Michael.

Re: start tls

[Steffen R. <ste...@sy...>]

Michael Str=F6der <mi...@st...> writes:

> Everything went well running (with web2ldap) against
> ldap.openldap.org but it failed when accessing www.nldap.com (Novell
> DS) or ldap.surfnet.nl (Netscape DS). I got segmentation faults.

Hmmmm. I don't have problems with it:

>>> import ldap
>>> s =3D ldap.open('ldap.surfnet.nl')
>>> s.simple_bind_s('','')
>>> s.search_s('', ldap.SCOPE_ONELEVEL, 'objectclass=3D*', ['objectclass'])
[('C=3DNL', {'objectclass': ['top',...

Can you run python inside gdb to get a traceback? Or give me more
details how you got the segfaults?

> The OpenLDAP 2.0-patches by Konstantin for python-ldap posted before
> on the mailing list worked. Maybe you already have a newer version
> of your patch?

No newer version, I can redo the diffs against CVS, but I'm not sure
whether this would help.

> I checked the shared libs. Seems ok to me.
>=20
> $ ldd _ldap.so=20
>         libldap.so.2 =3D> /usr/local/openldap2/lib/libldap.so.2
> (0x40023000)
>         liblber.so.2 =3D> /usr/local/openldap2/lib/liblber.so.2
> (0x4004e000)
>         libc.so.6 =3D> /lib/libc.so.6 (0x40058000)
>         libsasl.so.7 =3D> /usr/lib/libsasl.so.7 (0x4016b000)
>         libssl.so.0.9.6 =3D> /usr/lib/libssl.so.0.9.6 (0x40176000)
>         libcrypto.so.0.9.6 =3D> /usr/lib/libcrypto.so.0.9.6
> (0x4022e000)
>         /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x80000000)
>         libgdbm.so.2 =3D> /usr/lib/libgdbm.so.2 (0x402f2000)
>         libdl.so.2 =3D> /lib/libdl.so.2 (0x402fa000)
>         libcrypt.so.1 =3D> /lib/libcrypt.so.1 (0x402fd000)
>         libpam.so.0 =3D> /lib/libpam.so.0 (0x4032b000)
>         libresolv.so.2 =3D> /lib/libresolv.so.2 (0x40333000)

looks fine. on my Redhat 7.1 system I get libssl.so.1 and
libcrypt.so.1 instead, but I don't think that would make a difference.

libldap.so.2 is symlinked to libldap.so.2.0.6 (same for liblber.so),
i.e. openldap-2.0.11

/steffen

Re: start tls

[Michael <mi...@st...>]

Steffen,

sorry for following-up so late.

Steffen Ries wrote:
> 
> attached is a small (experimental) patch, which enables
> 'start_tls_s()' in python-ldap.

I built with your patch against OpenLDAP 2.0.11 and did some tests
without StartTLS first.

Everything went well running (with web2ldap) against
ldap.openldap.org but it failed when accessing www.nldap.com (Novell
DS) or ldap.surfnet.nl (Netscape DS). I got segmentation faults.

The OpenLDAP 2.0-patches by Konstantin for python-ldap posted before
on the mailing list worked. Maybe you already have a newer version
of your patch?

I checked the shared libs. Seems ok to me.

$ ldd _ldap.so 
        libldap.so.2 => /usr/local/openldap2/lib/libldap.so.2
(0x40023000)
        liblber.so.2 => /usr/local/openldap2/lib/liblber.so.2
(0x4004e000)
        libc.so.6 => /lib/libc.so.6 (0x40058000)
        libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4016b000)
        libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40176000)
        libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6
(0x4022e000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
        libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x402f2000)
        libdl.so.2 => /lib/libdl.so.2 (0x402fa000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x402fd000)
        libpam.so.0 => /lib/libpam.so.0 (0x4032b000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x40333000)

> I included Konstanin's patches and the memory leak fixes and have run
> the diff against the current CVS version. David's CIDict patches
> are not included, so I disabled CIDict to get it running with
> python2.1.

We'll drop CIDict anyway.

Ciao, Michael.

Re: Tagging the CVS archive

[Michael <mi...@st...>]

Konstantin,

sorry for answering that late.

Konstantin Chuguev wrote:
> 
> I think there's no point to postpone introduction of the OpenLDAPv1 branch
> in the CVS.

Agreed.

> I can do that, I just need an approval from one of the project
> admins.

Hmm, not sure if I'm a project admin. Well, I'm listed there...

> The proposed name is openldap_1_branch. It will be made on both 
> python-ldap and htdocs directories.

Please use capital letters OPENLDAP_1_BRANCH but not on the htdocs/
directory. Go for it.

> A small question: there are HTML links to files in htdocs/doc/ directory
> from htdocs/docs.shtml file, while there's no such directory. Why?

The directory htdocs/ is solely dedicated to manage the web pages on
http://python-ldap.sf.net. Leave that out. It's not part of a
release tar-ball.

Ciao, Michael.

Re: Returning sorted sets

[Michael <mi...@st...>]

ni...@br... wrote:
> 
> thanks for the anwer.  i 'm using openldap (not sure if this has server
> side sorting),

My OpenLDAP does not announce it in supportedControl. You can check
yourself with e.g. web2ldap:

http://sites.inka.de:8002/web2ldap/ldapurl?ldap://ldap.openldap.org

> but if it does, it may be worth me looking into the jndi
> before using caching.  boo hiss ;-)

Boooooo!

Maybe Jython?

Ciao, Michael.

Re: Returning sorted sets

[<ni...@br...>]

thanks for the anwer.  i 'm using openldap (not sure if this has server
side sorting), but if it does, it may be worth me looking into the jndi
before using caching.  boo hiss ;-)

nick

Michael Str=F6der wrote:
>=20
> ni...@Br... wrote:
> >
> > Ideally, I want my search interface to return just 20 records at a ti=
me,
> > which are a sorted subset of a larger result set.  Does the LDAP
> > protocol allow this?
>=20
> The right solution would require deploying two LDAP extended
> controls:
> - paged results (OID 1.2.840.113556.1.4.319, see RFC2696)
> - Server Side Sorting of Search Results
>   (OID 1.2.840.113556.1.4.473, see RFC2891)
>=20
> But unfortunately
> 1. with python-ldap you can't currently make use of extended
>    controls and
> 2. the server has to support both controls (which you can
>    check by looking at attribute supportedControl of its
>    RootDSE).
>=20
> > I'm trying to think how else to do a multiple-page
> > search interface, ala current search engines with the footer
>=20
> Well, you could retrieve all search results, sort them on the client
> side and cache it for the next page hits. But take care of security
> considerations!
>=20
> My web2ldap cheats: It simply invokes a async search and retrieves
> the search results for the currently viewed page without doing any
> sorting. I considered the user to give up looking through the search
> results on the first page anyway. ;-)
>=20
> Ciao, Michael.

--=20
Nick Bower, Intranet Developer
ni...@br...

Brainstorm
388 - 396 Oxford St
London W1N 9EH
United Kingdom
Tel 020 7074 7000
Mob 0790 5405 443
Fax 020 7074 7070

http://www.brainstorm.co.uk

Re: Returning sorted sets

[Michael <mi...@st...>]

ni...@Br... wrote:
> 
> Ideally, I want my search interface to return just 20 records at a time,
> which are a sorted subset of a larger result set.  Does the LDAP
> protocol allow this?

The right solution would require deploying two LDAP extended
controls:
- paged results (OID 1.2.840.113556.1.4.319, see RFC2696)
- Server Side Sorting of Search Results
  (OID 1.2.840.113556.1.4.473, see RFC2891)

But unfortunately
1. with python-ldap you can't currently make use of extended
   controls and
2. the server has to support both controls (which you can
   check by looking at attribute supportedControl of its
   RootDSE).

> I'm trying to think how else to do a multiple-page
> search interface, ala current search engines with the footer

Well, you could retrieve all search results, sort them on the client
side and cache it for the next page hits. But take care of security
considerations!

My web2ldap cheats: It simply invokes a async search and retrieves
the search results for the currently viewed page without doing any
sorting. I considered the user to give up looking through the search
results on the first page anyway. ;-)

Ciao, Michael.

Returning sorted sets

[<ni...@Br...>]

This one should really go in the FAQ for LDAP beginners like me :-)

I've implemented an LDAP search interface, but as we know, results are
returned unsorted.  Python doesn't do too badly at this (although I
can't help thinking it would be faster if underlying C routines did
it).  But sorting on the client side becomes problematic in a cgi which
wants to show just 20 results at a time.

Ideally, I want my search interface to return just 20 records at a time,
which are a sorted subset of a larger result set.  Does the LDAP
protocol allow this?  I'm trying to think how else to do a multiple-page
search interface, ala current search engines with the footer

[ 1 | 2 | 3 | 4 | next --> ]

Any ideas?

Cheers, nick

PS - Thanks for a useful tool.


Michael Str=F6der wrote:
>=20
> Steve Jones wrote:
> >
> > I have just installed the Win32 version of Zope 2.4.0 and it ships wi=
th
> > Python 2.1.  Your python-ldap module requires Python2.0 and apparentl=
y
> > won't work with python2.1.  Any chance of making a python2.1 verion o=
f
> > the ldap code available?
>=20
> Sorry, I just provide the ZIP file for download. I have no Win32
> environment for building python-ldap. Maybe you can convince Mauro
> who did it or another person.
>=20
> Ciao, Michael.
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> http://lists.sourceforge.net/lists/listinfo/python-ldap-dev

--=20
Nick Bower, Intranet Developer
ni...@br...

Brainstorm
388 - 396 Oxford St
London W1N 9EH
United Kingdom
Tel 020 7074 7000
Mob 0790 5405 443
Fax 020 7074 7070

http://www.brainstorm.co.uk

Re: Python-ldap32 module for Zope

[Michael <mi...@st...>]

Steve Jones wrote:
> 
> I have just installed the Win32 version of Zope 2.4.0 and it ships with
> Python 2.1.  Your python-ldap module requires Python2.0 and apparently
> won't work with python2.1.  Any chance of making a python2.1 verion of
> the ldap code available?

Sorry, I just provide the ZIP file for download. I have no Win32
environment for building python-ldap. Maybe you can convince Mauro
who did it or another person.

Ciao, Michael.

Re: Solaris 8 & python_ldap for Zope/Python

[Joe L. <jl...@op...>]

Robert, as an addendum, the Solaris 8 libs aren't the netscape libs (Sun=20=

has their own working code base). So, alternatively, you could use the=20=

netscape libraries or the mozilla versions if the OpenLDAP ones do not=20=

work. Michael is correct in that any logs of the builds will help out=20
list readers.

to the rest: yeah, I'm back in action, and happy to see a lot of list=20
traffic of late in positive directions. It looks like I may get to focus=20=

most of my energies on Zope since the effort on the OpenLDAP 2.x stuff=20=

is progressing nicely. One note: I'm hoping to resolve darwin/MacOSX=20
dynamic library issues since Zope folks seem to like MacOSX.

On Tuesday, July 31, 2001, at 08:49  AM, Michael Str=F6der wrote:

> Robert,
>
> sorry for answering so late.
>
> Robert Craven wrote:
>>
>> Has anyone tried to get this to work?
>>
>> Sorry if this has been covered, I am new to the list.  I am
>> trying to get Zope 2.4 + Python 2.1.1 + LDAP to work.
>> The LDAP libraries native to Solaris 8 seem to be missing a real
>> reference to ldap_name2template. At least that is what zope
>> complains about when it starts up.  I have the
>> python-ldap-1.10alpha3.  I have also tried to compile openldap
>> (versions 1.2.12 and 2.0.11) without any real success.
>
> I can't give you specific hints about building under Solaris 8 and
> the native LDAP libs with Solaris 8 (AFAIK it's the Netscape LDAP
> SDK).
>
> But I'd suggest that you check out the latest snapshot of
> python-ldap and try to build that against a local copy of the
> OpenLDAP 1.2.12 tree. Support for OpenLDAP 2 libs is work in
> progress and currently very experimental.
>
> If you have problems the most promising way is to come up with the
> build log on this mailing list.
>
> Ciao, Michael.
>
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> http://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: Solaris 8 & python_ldap for Zope/Python

[Michael <mi...@st...>]

Robert,

sorry for answering so late.

Robert Craven wrote:
> 
> Has anyone tried to get this to work?
> 
> Sorry if this has been covered, I am new to the list.  I am
> trying to get Zope 2.4 + Python 2.1.1 + LDAP to work.
> The LDAP libraries native to Solaris 8 seem to be missing a real
> reference to ldap_name2template. At least that is what zope
> complains about when it starts up.  I have the
> python-ldap-1.10alpha3.  I have also tried to compile openldap
> (versions 1.2.12 and 2.0.11) without any real success.

I can't give you specific hints about building under Solaris 8 and
the native LDAP libs with Solaris 8 (AFAIK it's the Netscape LDAP
SDK).

But I'd suggest that you check out the latest snapshot of
python-ldap and try to build that against a local copy of the
OpenLDAP 1.2.12 tree. Support for OpenLDAP 2 libs is work in
progress and currently very experimental.

If you have problems the most promising way is to come up with the
build log on this mailing list.

Ciao, Michael.

Solaris 8 & python_ldap for Zope/Python

[Robert C. <Rob...@em...>]

Has anyone tried to get this to work?

Sorry if this has been covered, I am new to the list.  I am
trying to get Zope 2.4 + Python 2.1.1 + LDAP to work.
The LDAP libraries native to Solaris 8 seem to be missing a real
reference to ldap_name2template. At least that is what zope
complains about when it starts up.  I have the
python-ldap-1.10alpha3.  I have also tried to compile openldap
(versions 1.2.12 and 2.0.11) without any real success.

Any help would be greatly appreciated.

Thanks,

Bob Craven

--
=============================================================================
Robert Craven                 AVS  DSCS (Design Software & Computer Services)
Motorola, Inc. 6501 William Cannon Dr. West MS.OE-320          (512) 895-4440
Austin, TX  78735-8598          <><               Rob...@mo...

Re: _ldap.SIZELIMIT_EXCEEDED

[Jens V. <je...@zo...>]

excellent, that was it ("sizelimit" directive in slapd.conf)

jens


On Friday, July 27, 2001, at 10:00 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>>
>> i am coming across the SIZELIMIT_EXCEEDED exception in some of my =
code=20
>> and
>> i was wondering what the limit actually is
>
> This is the server-side limit of maximum search results. You usually
> do not have any influence on that because it depends on the LDAP
> server's configuration.
>
> Ciao, Michael.

Re: _ldap.SIZELIMIT_EXCEEDED

[Michael <mi...@st...>]

Jens Vagelpohl wrote:
> 
> i am coming across the SIZELIMIT_EXCEEDED exception in some of my code and
> i was wondering what the limit actually is

This is the server-side limit of maximum search results. You usually
do not have any influence on that because it depends on the LDAP
server's configuration.

Ciao, Michael.

_ldap.SIZELIMIT_EXCEEDED

[Jens V. <je...@zo...>]

hi everyone,

i am coming across the SIZELIMIT_EXCEEDED exception in some of my code and 
i was wondering what the limit actually is and if there is a way to code 
around it when using python-ldap, or maybe even a switch in the 
python-ldap code that i could change and then recompile?

jens

(no subject)

[Marc C. <mar...@ya...>]

  Hi, I'm testing the web2ldap software, but it's
being impossible to me to install it.

  I'm trying to install it in a Windows system, so I
downloaded the software, the libs and Phyton, I put
the dlls in the right folder, I ran Python, I loaded
the web2ldap.py script in the sbin folder and when I
tried to ran it, I obtained the following error:

Traceback (innermost last):
  File "C:\web2ldap-0.9.4\sbin\web2ldap.py", line 33,
in ?
    import
w2lcore,w2lhandler,msHTTPServer,msHTTPHandler,ipadr
  File "C:\web2ldap-0.9.4\pylib\w2lhandler.py", line
11, in ?
    import sys,os,time,socket,msshelve,msgzip,\
  File "C:\web2ldap-0.9.4\pylib\ldapdns.py", line 25,
in ?
    DNS.ParseResolvConf()
  File "C:\web2ldap-0.9.4\pylib\DNS\Base.py", line 18,
in ParseResolvConf
    lines=open("/etc/resolv.conf").readlines()
IOError: [Errno 2] No such file or directory:
'/etc/resolv.conf'


I looked for the resolv.conf file in my computer and
it seems not to exist, so, how can I fix it?

Thanks,
      Marc


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

Re: Tagging the CVS archive

[Konstantin C. <Kon...@da...>]

Hi All,

I think there's no point to postpone introduction of the OpenLDAPv1 branch
in the CVS. I can do that, I just need an approval from one of the project
admins.
The proposed name is openldap_1_branch. It will be made on both python-ldap
and htdocs directories.
After that we could just reflect branching in htdocs/faq.shtml (or
somewhere else) and then update the latter in the current branch to reflect
LDAPv3/OpenLDAPv2 support (after submitting the corresponding patches, of
course :-)

Any objections?

A small question: there are HTML links to files in htdocs/doc/ directory
from htdocs/docs.shtml file, while there's no such directory. Why?

Regards,
    Konstantin.

--
         * *       Konstantin Chuguev           Francis House
      *      *     Application Engineer         112 Hills Road
    *              Tel: +44 1223 302992         Cambridge CB2 1PQ
D  A  N  T  E      WWW: http://www.dante.net    United Kingdom

Re: Tagging the CVS archive

[Steffen R. <ste...@sy...>]

Konstantin Chuguev <Kon...@da...> writes:

...
> >     I would suggest a scheme where upper case tags are applied to
> >     releases, and lower case tags are branches.
> >
> >     e.g.:
> >     REL-1-10ALPHA3
> >     REL-1-11
> >     ...
> >     openldap-1-api
> >     ...
> >
> Are you sure the tags are case sensitive?

Yes.

> The other thing: I'd personally prefer (I'm not insisting though :-) "_"
> instead of "-".

Works for me too :-) (I was used to "." for separating parts of tags,
but this works with ClearCase, not with CVS, so I started to use -
instead...)

> In any case, if we're going to have branches dependant on the OpenLDAP
> API support, they could be called just OPENLDAP_1 or similar, while
> releases could be named REL_1_11 and REL_1_10.

I think it is better to have some naming convention which
distinguishes branches from releases. E.g. "openldap_1_branch".
 
> Unfortunately, I don't have enough experience in CVS to make branches.
> Could somebody do that?

cvs tag -b <branchname>
vs.
cvs tag <tagname>

I don't have access to CVS...

/steffen
-- 
ste...@sy...	<> Gravity is a myth -- the Earth sucks!

Re: Tagging the CVS archive

[Michael <mi...@st...>]

Konstantin Chuguev wrote:
> 
> In any case, if we're going to have branches dependant on the OpenLDAP
> API support, they could be called just OPENLDAP_1 or similar, while
> releases could be named REL_1_11 and REL_1_10.

Today nobody is building with Netscape or Novell libs anymore, I
guess.

Branches for OpenLDAP API (e.g OPENLDAP_1 and OPENLDAP_2) and tags
for releases (e.g. REL_1_11). Does that make sense to you folks?

> Unfortunately, I don't have enough experience in CVS to make branches.

Me too.

> Could somebody do that?

David?

Ciao, Michael.