perl-ldap-dev

Re: International Characters

[Christoph N. <en...@ap...>]

On Tue, 5 Jun 2001, Knut Sander wrote:

> Christoph Neumann wrote:
> > On Tue, 5 Jun 2001, Knut Sander wrote:
> > > > I chose the directoryString (UTF-8 format) type since it should all=
ow the
> > > > international characters.  However, when I try to insert the string=
 'im
> > > > k=3DE4ppele 8' I get the error:
> > > >
> > > > apuhomestreet: value #0 contains invalid data
> > >
> > > Hi Christoph,
> > >
> > > did you encode your data as UTF8-string? The 0xe4 above (=E4 =3D ae) =
looks
> > > like you try to add a latin1 string, but this is not a legal UTF8 byt=
e
> > > sequence.
> >=20
> > Hm...that seems to be correct.  I checked the output from the "debug".
> > This is the string I am sending to the server:
> > 0040 04 13:  STRING =3D 'apuhomestreet'
> > 004F 31 14:  SET {
> > 0051 04 12:    STRING
> > 0053      :      69 6D 20 6B E4 70 70 65 6C 65 20 38 __ __ __ __ im k.p=
pele 8
> > 005F      :  }
>=20
> ok - E4 for ae is latin1, UTF8 needs 2 bytes for this.
>=20
> > Any recommendation on which encoding I should user in LDAP to support
> > international characters?  Is UTF8 really the way to go?
> I think it is way =3D)
> =20
> > If UTF8 is the way to go, how should I go about converting data that is
> > in iso-8859-1 to UTF8?  A quick search on CPAN turned up
> > "Unicode::MapUTF8" and "use utf8" pragma in perl 5.7.  Anyone have
> > experience with either of these?
> >=20
> > Also, where might I find good documentation on how these character sets
> > are defined?
>=20
> I used Unicode::String, take a look at the example on perldoc
> Unicode::String, it work well and is easy to handle. I have good
> experiences by building the en/decoding into the application specific
> LDAP-layer (you allways need this for larger applications =3D)

Great!  I checked it out.  It looks like a great library.

> 'use utf8' in perl 5.6/7 may do this job now on the fly, but I did not
> play with it until now, because I can't use 5.6 on productive systems at
> the moment =3D(.

You and find more information about the new pragma at:
http://search.cpan.org/doc/JHI/perl-5.7.1/lib/utf8.pm
that also links to:
http://search.cpan.org/doc/JHI/perl-5.7.1/pod/perlunicode.pod

> Some pointer for this would be welcome =3D)
>=20
> - Knut

Re: International Characters

[Knut S. <knu...@se...>]

Christoph Neumann wrote:
> On Tue, 5 Jun 2001, Knut Sander wrote:
> > > I chose the directoryString (UTF-8 format) type since it should allow the
> > > international characters.  However, when I try to insert the string 'im
> > > k=E4ppele 8' I get the error:
> > >
> > > apuhomestreet: value #0 contains invalid data
> >
> > Hi Christoph,
> >
> > did you encode your data as UTF8-string? The 0xe4 above (ä = ae) looks
> > like you try to add a latin1 string, but this is not a legal UTF8 byte
> > sequence.
> 
> Hm...that seems to be correct.  I checked the output from the "debug".
> This is the string I am sending to the server:
> 0040 04 13:  STRING = 'apuhomestreet'
> 004F 31 14:  SET {
> 0051 04 12:    STRING
> 0053      :      69 6D 20 6B E4 70 70 65 6C 65 20 38 __ __ __ __ im k.ppele 8
> 005F      :  }

ok - E4 for ae is latin1, UTF8 needs 2 bytes for this.

> Any recommendation on which encoding I should user in LDAP to support
> international characters?  Is UTF8 really the way to go?
I think it is way =)
 
> If UTF8 is the way to go, how should I go about converting data that is
> in iso-8859-1 to UTF8?  A quick search on CPAN turned up
> "Unicode::MapUTF8" and "use utf8" pragma in perl 5.7.  Anyone have
> experience with either of these?
> 
> Also, where might I find good documentation on how these character sets
> are defined?

I used Unicode::String, take a look at the example on perldoc
Unicode::String, it work well and is easy to handle. I have good
experiences by building the en/decoding into the application specific
LDAP-layer (you allways need this for larger applications =)

'use utf8' in perl 5.6/7 may do this job now on the fly, but I did not
play with it until now, because I can't use 5.6 on productive systems at
the moment =(.

Some pointer for this would be welcome =)

- Knut

__________________________________________
SecureNet GmbH - http://www.secure-net.de/

Re: International Characters

[Christoph N. <en...@ap...>]

On Tue, 5 Jun 2001, Knut Sander wrote:

> > I chose the directoryString (UTF-8 format) type since it should allow t=
he
> > international characters.  However, when I try to insert the string 'im
> > k=3DE4ppele 8' I get the error:
> >=20
> > apuhomestreet: value #0 contains invalid data
>=20
> Hi Christoph,
>=20
> did you encode your data as UTF8-string? The 0xe4 above (=E4 =3D ae) look=
s
> like you try to add a latin1 string, but this is not a legal UTF8 byte
> sequence.

Hm...that seems to be correct.  I checked the output from the "debug". =20
This is the string I am sending to the server:
0040 04 13:  STRING =3D 'apuhomestreet'
004F 31 14:  SET {
0051 04 12:    STRING
0053      :      69 6D 20 6B E4 70 70 65 6C 65 20 38 __ __ __ __ im k.ppele=
 8
005F      :  }

Any recommendation on which encoding I should user in LDAP to support
international characters?  Is UTF8 really the way to go?

If UTF8 is the way to go, how should I go about converting data that is=20
in iso-8859-1 to UTF8?  A quick search on CPAN turned up
"Unicode::MapUTF8" and "use utf8" pragma in perl 5.7.  Anyone have
experience with either of these?

Also, where might I find good documentation on how these character sets
are defined?

Thanks for all the help and insight.

- Christoph

Re: International Characters

[Chris R. <chr...@me...>]

Knut Sander <knu...@se...> wrote:
>> Date: Fri, 1 Jun 2001 19:21:40 -0700 (PDT)
>> From: Christoph Neumann <en...@ap...>
>> To: LDAP Mailing List <per...@li...>
>> Subject: International Characters
>  =
>> I chose the directoryString (UTF-8 format) type since it should allow =
the
>> international characters.  However, when I try to insert the string 'im
>> k=3DE4ppele 8' I get the error:
>> =
>> apuhomestreet: value #0 contains invalid data
> =
> Hi Christoph,
> =
> did you encode your data as UTF8-string? The 0xe4 above (=E4 =3D ae) =
looks
> like you try to add a latin1 string, but this is not a legal UTF8 byte
> sequence.
> =
> I also had this problem with OpenLDAP 2.x but not with Netscape or
> ControlData. It looks to me, that it depends on the schema, ControlData
> (real X.500) defines attributes with more then on legal encoding (T.61,
> latin1, UTF8) and prefixes it with '{<encoding>}' like passwords. The
> server tries to determine the right encoding if it is not supplied, and
> falls back to T.61 if it is not clear. I don't know if this is conform
> to any LDAP-spec.

That isn't legal for the standard syntaxes in LDAPv3 - everything *must* be
UTF-8. It would be OK for LDAPv2, except that UTF-8 is not a valid encoding
of a character set for LDAPv2.

Netscape will typically accept any illegal garbage values and return them
verbatim, so it isn't a good test of what is correct or not :-(

Cheers,

Chris

Re: International Characters

[Knut S. <knu...@se...>]

> Date: Fri, 1 Jun 2001 19:21:40 -0700 (PDT)
> From: Christoph Neumann <en...@ap...>
> To: LDAP Mailing List <per...@li...>
> Subject: International Characters
 
> I chose the directoryString (UTF-8 format) type since it should allow the
> international characters.  However, when I try to insert the string 'im
> k=E4ppele 8' I get the error:
> 
> apuhomestreet: value #0 contains invalid data

Hi Christoph,

did you encode your data as UTF8-string? The 0xe4 above (ä = ae) looks
like you try to add a latin1 string, but this is not a legal UTF8 byte
sequence.

I also had this problem with OpenLDAP 2.x but not with Netscape or
ControlData. It looks to me, that it depends on the schema, ControlData
(real X.500) defines attributes with more then on legal encoding (T.61,
latin1, UTF8) and prefixes it with '{<encoding>}' like passwords. The
server tries to determine the right encoding if it is not supplied, and
falls back to T.61 if it is not clear. I don't know if this is conform
to any LDAP-spec.

-Knut

__________________________________________
SecureNet GmbH - http://www.secure-net.de/

Re: somewhat off topic

[Chris R. <chr...@me...>]

Justin <da...@io...> wrote:
> Hello,
> 
> This posting is probably off topic, but what I'm looking for is a good 
> place to ask such a question, so I thought maybe one of the bright perl
> god(esse)s here could point me in the proper direction of asking.
> 
> Thanks!
> 
> 
>> I am trying to figure out a way to link LDAP entries together in such a
>> way that it will be easy to read one object and then follow the links to
>> read the connected objects as well.  The "linkee" may be linked to by
>> more than one "linker"
>> 
>> Currently it seems that the best way to do this is to add an
>> attributetype of syntax DN to the schema for the objectclasses I'm
>> planning to work with.

Yes, that's the only standard way.

>> I was wondering if anyone else had some ideas about other possible ways
>> of tackling this problem.  What would be really nice is if there were a
>> way to read the 'head' object and all linked objects in a single
>> operation!
>> 
>> Thanks in advance for any suggestions,
>>  Justin Cooper

No, that's not currently possible.

The current drafts of X.500 support heirarchical relationships between
entries independant of the DIT structure, and it is possible to request
that a read operation returns the entire family.

You may want to investigate that option; there are internet drafts around
which describe the mapping of these features into LDAP.

Cheers,

Chris

somewhat off topic

[Justin <da...@io...>]

Hello,

This posting is probably off topic, but what I'm looking for is a good 
place to ask such a question, so I thought maybe one of the bright perl
god(esse)s here could point me in the proper direction of asking.

Thanks!


> I am trying to figure out a way to link LDAP entries together in such a way
> that it will be easy to read one object and then follow the links to read
> the connected objects as well.  The "linkee" may be linked to by more than
> one "linker"
> 
> Currently it seems that the best way to do this is to add an attributetype
> of syntax DN to the schema for the objectclasses I'm planning to work with.
> 
> I was wondering if anyone else had some ideas about other possible ways of
> tackling this problem.  What would be really nice is if there were a way
> to read the 'head' object and all linked objects in a single operation!
> 
> Thanks in advance for any suggestions,
>  Justin Cooper
> 

Re: Installing Net::LDAPapi problems.

[Chris R. <chr...@me...>]

Chua Kong Sian <kon...@ya...> wrote:
> Hi.  I'm encoutering errors during installation of
> NET::LDAPapi 1.42 on Solaris 2.6.  The errors are
> variables "na" and "sv_undef" are undefined.  I tried
> declaring "int na" and "SV sv_undef" in the various
> functions, but after installation, the test didn't
> work.
> 
> Any clues?  I've already installed Netscape SDK 3
> files into /usr/local/lib & /usr/local/include. 
> Thanks.
> 
> Kong Sian
> 
> 
> 
> cp LDAPapi.pm blib/lib/Net/LDAPapi.pm

You're asking the wrong list! This list is for perl-ldap, which provides
the Net::LDAP class and subclasses. It is 100% perl and doesn't need an
external LDAP library.

Check the README in your module to find out who to ask.

Cheers,

Chris

Installing Net::LDAPapi problems.

[Chua K. S. <kon...@ya...>]

Hi.  I'm encoutering errors during installation of
NET::LDAPapi 1.42 on Solaris 2.6.  The errors are
variables "na" and "sv_undef" are undefined.  I tried
declaring "int na" and "SV sv_undef" in the various
functions, but after installation, the test didn't
work.

Any clues?  I've already installed Netscape SDK 3
files into /usr/local/lib & /usr/local/include. 
Thanks.

Kong Sian



cp LDAPapi.pm blib/lib/Net/LDAPapi.pm
AutoSplitting blib/lib/Net/LDAPapi.pm
(blib/lib/auto/Net/LDAPapi)
/usr/local/bin/perl constant.gen >constant.h
/usr/local/bin/perl
-I/usr/local/lib/perl5/5.6.1/sun4-solaris
-I/usr/local/lib/perl5/5.6.1
/usr/local/lib/perl5/5.6.1/ExtUtils/xsubpp  -typemap
/usr/local/lib/perl5/5.6.1/ExtUtils/typemap -typemap
typemap LDAPapi.xs > LDAPapi.xsc && mv LDAPapi.xsc
LDAPapi.c
gcc -c -I/usr/local/include -fno-strict-aliasing
-I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O    -DVERSION=\"1.42\" 
-DXS_VERSION=\"1.42\" -fPIC
-I/usr/local/lib/perl5/5.6.1/sun4-solaris/CORE
-DNETSCAPE_LDAP LDAPapi.c
LDAPapi.xs: In function `av2modvals':
LDAPapi.xs:95: `na' undeclared (first use in this
function)
LDAPapi.xs:95: (Each undeclared identifier is reported
only once
LDAPapi.xs:95: for each function it appears in.)
LDAPapi.xs: In function `parse1mod':
LDAPapi.xs:197: `na' undeclared (first use in this
function)
LDAPapi.xs: In function `XS_Net__LDAPapi_ldap_search':
LDAPapi.xs:578: `na' undeclared (first use in this
function)
LDAPapi.xs: In function
`XS_Net__LDAPapi_ldap_search_s':
LDAPapi.xs:614: `na' undeclared (first use in this
function)
LDAPapi.xs: In function
`XS_Net__LDAPapi_ldap_search_st':
LDAPapi.xs:660: `na' undeclared (first use in this
function)
LDAPapi.xs: In function
`XS_Net__LDAPapi_ldap_url_parse':
LDAPapi.xs:1137: `sv_undef' undeclared (first use in
this function)
LDAPapi.xs: In function
`XS_Net__LDAPapi_ldap_multisort_entries':
LDAPapi.xs:1221: `na' undeclared (first use in this
function)
*** Error code 1
make: Fatal error: Command failed for target
`LDAPapi.o'


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Re: International Characters

[Chris R. <chr...@me...>]

Christoph Neumann <en...@ap...> wrote:
> =
> I'm using OpenLDAP 2.0.11 with perlldap 0.23.  I'm trying to insert
> international characters into the directory.  I'm wondering if I need to
> do anything special with perlldap inorder to achive this feat, or if my
> problem is entirely dependant on OpenLDAP.
> =
> Here's what I have in the schema
> =
> attributetype ( 1.3.6.1.4.1.96419.1.1.13
>     NAME          'apuHomeStreet'
>     DESC          'Street address for home mailing address'
>     EQUALITY      caseExactMatch
>     SUBSTR        caseIgnoreSubstringsMatch
>     SINGLE-VALUE
>     SYNTAX        1.3.6.1.4.1.1466.115.121.1.15{100} )
> =
> I chose the directoryString (UTF-8 format) type since it should allow the
> international characters.  However, when I try to insert the string 'im
> k=E4ppele 8' I get the error:
> =
> apuhomestreet: value #0 contains invalid data
> =
> - Christoph

The schema entry looks correct. What were the actual bytes in your string,
and what were the actual bytes sent to the server? What version of perl
were you using?

It is possible that you were entering characters using a different
character set (eg ISO 8859-1) which of course are not UTF-8. I don't think
Net::LDAP does any magic translation of character sets (it doesn't know
enough to be able to do this) though I'm not too sure what perl 5.6 will do
for you here.

To see the actual bytes going to the server, create the Net::LDAP object
using debug =3D> 8:

	$ldap =3D Net::LDAP->new('hostname', debug =3D> 8);

Cheers,

Chris

International Characters

[Christoph N. <en...@ap...>]

I'm using OpenLDAP 2.0.11 with perlldap 0.23.  I'm trying to insert
international characters into the directory.  I'm wondering if I need to
do anything special with perlldap inorder to achive this feat, or if my
problem is entirely dependant on OpenLDAP.

Here's what I have in the schema

attributetype ( 1.3.6.1.4.1.96419.1.1.13
    NAME          'apuHomeStreet'
    DESC          'Street address for home mailing address'
    EQUALITY      caseExactMatch
    SUBSTR        caseIgnoreSubstringsMatch
    SINGLE-VALUE
    SYNTAX        1.3.6.1.4.1.1466.115.121.1.15{100} )

I chose the directoryString (UTF-8 format) type since it should allow the
international characters.  However, when I try to insert the string 'im
k=E4ppele 8' I get the error:

apuhomestreet: value #0 contains invalid data

- Christoph

Re: [Fwd] Problem with Net::LDAP

[Simon A. <sim...@st...>]

> Entry will not be defined on the last call, so make sure you check it is defined.
> Also to save memoery you need to tell Net::LDAP to remove it from the list.
>
>  sub check_oracle {
>          my ($mesg, $entry) = @_;
>
>          if ($entry and $entry->isa('Net::LDAP::Entry')) {
>               $entry->dump();
>               $mesg->pop_entry;
>          }
>  }
>
> Graham.

Thanks heaps for that Graham. It works wonders :-)


Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: sim...@st...

The real fighting men and women of the 21st century will continue
to be techo's backed up by the grunts with bad haircuts and rifles.

Re: [Fwd] Problem with Net::LDAP

[Christoph N. <en...@ap...>]

On Thu, 31 May 2001, Graham Barr wrote:

> On Thu, May 31, 2001 at 08:12:39AM -0500, Clif Harden wrote:
> > > 
> > > Entry will not be defined on the last call, so make sure you check it is defined.
> > > Also to save memoery you need to tell Net::LDAP to remove it from the list.
> > > 
> > >  sub check_oracle {
> > >          my ($mesg, $entry) = @_;
> > >  
> > >          if ($entry and $entry->isa('Net::LDAP::Entry')) {
> > >               $entry->dump();
> > >               $mesg->pop_entry;
> > >          }
> > >  }
> > > 
> > > Graham.
> > > 
> > > 
> > 
> > Graham,
> > 
> > We need to document entry->dump method. 
> > I do not see it listed in the online documentation.
> 
> It needs to be fixed first to use Net::LDAP::LDIF
> 
> > The mesg->pop_entry method probably needs to be listed in the 
> > Message documentation too, I could currently only find it in the
> > Seach documentation.
> 
> No, Net::LDAP::Search is the right place. It is not a method in
> Net::LDAP::Message. Net::LDAP::Search is a sub-class of Net::LDAP::Message
> that is returned by ->search. It is here that the pop_entry method
> is defined.
> 
> Graham.
> 
> > 
> > This info will probably be put into the FAQ in a new callback section.
> > 

I think an explaination of how to create a callback that removes each
entry as it comes should definitely be put in the FAQ.  I recall having to
read through the source code in order to figure this out before.  Knowing
how to do this is indespensible if one needs to process large numbers of
entries from LDAP.

- Christoph


> > Regards,
> > 
> > Clif Harden
> > 
> 
> 

Re: [Fwd] Problem with Net::LDAP

[Graham B. <gb...@po...>]

On Thu, May 31, 2001 at 08:12:39AM -0500, Clif Harden wrote:
> > 
> > Entry will not be defined on the last call, so make sure you check it is defined.
> > Also to save memoery you need to tell Net::LDAP to remove it from the list.
> > 
> >  sub check_oracle {
> >          my ($mesg, $entry) = @_;
> >  
> >          if ($entry and $entry->isa('Net::LDAP::Entry')) {
> >               $entry->dump();
> >               $mesg->pop_entry;
> >          }
> >  }
> > 
> > Graham.
> > 
> > 
> 
> Graham,
> 
> We need to document entry->dump method. 
> I do not see it listed in the online documentation.

It needs to be fixed first to use Net::LDAP::LDIF

> The mesg->pop_entry method probably needs to be listed in the 
> Message documentation too, I could currently only find it in the
> Seach documentation.

No, Net::LDAP::Search is the right place. It is not a method in
Net::LDAP::Message. Net::LDAP::Search is a sub-class of Net::LDAP::Message
that is returned by ->search. It is here that the pop_entry method
is defined.

Graham.

> 
> This info will probably be put into the FAQ in a new callback section.
> 
> Regards,
> 
> Clif Harden
> 

Re: [Fwd] Problem with Net::LDAP

[Clif H. <cl...@di...>]

> 
> Entry will not be defined on the last call, so make sure you check it is defined.
> Also to save memoery you need to tell Net::LDAP to remove it from the list.
> 
>  sub check_oracle {
>          my ($mesg, $entry) = @_;
>  
>          if ($entry and $entry->isa('Net::LDAP::Entry')) {
>               $entry->dump();
>               $mesg->pop_entry;
>          }
>  }
> 
> Graham.
> 
> 

Graham,

We need to document entry->dump method. 
I do not see it listed in the online documentation.

The mesg->pop_entry method probably needs to be listed in the 
Message documentation too, I could currently only find it in the
Seach documentation.

This info will probably be put into the FAQ in a new callback section.

Regards,

Clif Harden

UNSUBSCRIBE

[christophe O. <chr...@ce...>]

-----Message d'origine-----
De : per...@li...
[mailto:per...@li...]De la part de Clif
Harden
Envoy=E9 : mercredi 30 mai 2001 03:46
=C0 : Simon Allard
Cc : LDAP Mailing List
Objet : Re: [Fwd] Problem with Net::LDAP


Simon Allard wrote:
>
> > > This is true, however 95000 * 200 bytes (rough size of the example
entry)
> > > only comes to about 18 megabytes, and Simon said his perl process w=
as
using
> > > 250 megabytes :-(
> > >
> > > That's a lot of overhead, unless Simon missed a zero out of his ent=
ry
count
> > > - 950000 entries would work out to use about the observed quantity =
of
> > > memory. Well, the same order of magnitude anyway.
> >
> > It would be nice to know what version of perl he is running
> > and on what type of systems.
>
> Output from perl -v
> This is perl, version 5.003 with EMBED
>         built under solaris at Jun 10 1998 02:26:14
>         + suidperl security patch
>
> The perl is the version that comes with Oracle 9i.
>
> delphi:~$ uname -a
> SunOS delphi.ihug.co.nz 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-2
>
> Simon Allard (Senior Tool Monkey)
> IHUG
> Ph (09) 358-5067   Email: sim...@st...
>
> The real fighting men and women of the 21st century will continue
> to be techo's backed up by the grunts with bad haircuts and rifles.


Simon,

The lowest version of perl that we support is version 5.004.
Very soon we will only support 5.005_03 and above.

IMO your problem is in your version of perl.

Regards,

Clif Harden          ch...@po...

Re: [Fwd] Problem with Net::LDAP

[Graham B. <gb...@po...>]

On Thu, May 31, 2001 at 03:01:26PM +1200, Simon Allard wrote:
> Thanks for the Reply Graham.
> 
> Callbacks sound like a great idea, but I am not having much luck with
> them. There isn't much documentation about them. I have tried in on my
> Solaid box with perl 5.003 and my Debian box  with perl 5.6 and get the
> same result.
> 
> Source follows:

> $ldap->search(
>         base => "$authbase",
>         filter => '(objectclass=ihugAuthAccount)',
> 	callback => &check_oracle()
> );

You need to pass a reference to the sub. This calls the sub and passes
its result.

  callback => \&check_oracle


> sub check_oracle {
>         my ($mesg, $entry) = @_;
> 
>         $entry->dump();
> }

Entry will not be defined on the last call, so make sure you check it is defined.
Also to save memoery you need to tell Net::LDAP to remove it from the list.

 sub check_oracle {
         my ($mesg, $entry) = @_;
 
         if ($entry and $entry->isa('Net::LDAP::Entry')) {
              $entry->dump();
              $mesg->pop_entry;
         }
 }

Graham.

[Fwd] Is perldap thread-safe ?

[Graham B. <gb...@po...>]

----- Forwarded message from "Gann, Leopold" <leo...@ic...> -----

Date: Thu, 31 May 2001 08:29:10 +0200
To: "'gb...@po...'" <gb...@po...>
From: "Gann, Leopold" <leo...@ic...>
Subject: Is perldap thread-safe ?
X-Mailer: Internet Mail Service (5.5.2653.19)

Hello Graham,

I really appreciated it using perl threads for more than a year. Now, I 
want to get more experience in perldap as well. Thus, the question to 
me is, can I run (perl)ldap searches each started in a separate perl 
thread ? Are there any side effects ? My experience is, there are
some. But, to be honest, I don't know at all, whether perldap was 
ever released for that.

If you don't know about either, maybe there is anyone else who 
experienced in that way ...

Thanks for your help,
Leo.
----------------------------------------------------------------------------
-----------------------------
Leopold Gann, Siemens AG, Otto-Hahn-Ring 6, 81730 Munich, Germany
Email:  Leo...@ic...
SiemensOfficePhone. :  	+49-89-636-46143   ( Wednesday and Friday ) 
SiemensOfficeFax: 	+49-89-636-45860
HomeOfficePhone:	+43-7742-58115



----- End forwarded message -----

Re: [Fwd] Problem with Net::LDAP

[Simon A. <sim...@st...>]

Thanks for the Reply Graham.

Callbacks sound like a great idea, but I am not having much luck with
them. There isn't much documentation about them. I have tried in on my
Solaid box with perl 5.003 and my Debian box  with perl 5.6 and get the
same result.

Source follows:

#!/usr/bin/perl

use strict;
use Net::LDAP;

my $authbase = "ou=auth, dc=ihug, dc=co, dc=nz";
my $authpass = "secret";


# Connect and bind to the LDAP Database
my $ldap = Net::LDAP->new('delphi.ihug.co.nz') or do {
	print "Couldn't connect to LDAP database $@\n";
	exit 1;
};

if (!$ldap->bind("cn=Manager, $authbase", password => $authpass)) {
	print "Ldap Bind failed!\n";
	exit 1;
}

$ldap->search(
        base => "$authbase",
        filter => '(objectclass=ihugAuthAccount)',
	callback => &check_oracle()
);


sub check_oracle {
        my ($mesg, $entry) = @_;

        $entry->dump();
}


When I run this I get:
delphi:~$ ./ldap-test.pl
Can't call method "dump" on an undefined value at ./ldap-test.pl line 31.

It looks like its calling the right sub, but its not getting passed the
varables? Any ideas why?

Thanks in Advance

- Simon Allard



> If this is not possible, try using the callback option. This allows you
> to process each entry as it arrives from the server.
>
> Graham.
>
> On Tue, May 29, 2001 at 09:41:54AM +0100, Graham Barr wrote:
> > ----- Forwarded message from Simon Allard <sim...@st...> -----
> >
> > Date: Tue, 29 May 2001 17:51:59 +1200 (NZST)
> > To: <gb...@po...>
> > From: Simon Allard <sim...@st...>
> > Subject: Problem with Net::LDAP
> >
> > Hey Graham.
> >
> > I am hopeing you can shed some light on this. I have this problem where
> > your module seems to chew up a lot of memory.
> >
> > I am running openldap 2.0.7 with perl-ldap-0.23.
> >
> > In openldap I have Aprox 95000 entrys. Each entry looks similar to this:
> >
> > dn:loginName=dbs, ou=auth, dc=domain, dc=co, dc=nz
> > objectclass: AuthAccount
> > loginName: dbs
> > userPassword: {crypt}sgaCZydxWDFD
> > nasAccess: SOMETHING
> > smtpAuth: 0
> > overrideProfile: 1
> > multicast: 0
> >
> > When I do a basic search eg:
> >
> > if (!$ldap->bind("cn=Manager, $authbase", password => $authpass, async => 1)) {
> > 	print "Ldap Bind failed!\n";
> > 	exit 1;
> > }
> > my $mesg = $ldap->search(
> >         base => "$authbase",
> >         filter => '(objectclass=ihugAuthAccount)'
> >        );
> >
> > $ldap->unbind;
> >
> > This search seems to chew up over 250meg of Ram. It pretty much makes the
> > perl module unusable. Do you have any suggestions on how I could get the
> > memory usage down to something reasonable?
> >
> > Also doing the unbind seems to take a very long time :(
> >
> > Hope you can help.
> > Thanks in Advance.
> >
> > Regards
> > Simon Allard
> >
> >
> >
> > Simon Allard (Senior Tool Monkey)
> > IHUG
> > Ph (09) 358-5067   Email: sim...@st...
> >
> > The real fighting men and women of the 21st century will continue
> > to be techo's backed up by the grunts with bad haircuts and rifles.
> >
> >
> > ----- End forwarded message -----
>

Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: sim...@st...

The real fighting men and women of the 21st century will continue
to be techo's backed up by the grunts with bad haircuts and rifles.

Re: [Fwd] Problem with Net::LDAP

[Simon A. <sim...@st...>]

> > Output from perl -v
> > This is perl, version 5.003 with EMBED
> >         built under solaris at Jun 10 1998 02:26:14
> >         + suidperl security patch
> >
> > The perl is the version that comes with Oracle 9i.
> >
> > delphi:~$ uname -a
> > SunOS delphi.ihug.co.nz 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-2
> Simon,
>
> The lowest version of perl that we support is version 5.004.
> Very soon we will only support 5.005_03 and above.
>
> IMO your problem is in your version of perl.

I have just tried it on my debian box.

soundy@zippie:~$ uname -a
Linux zippie 2.2.18 #2 Thu Apr 5 00:56:03 NZST 2001 i686 unknown


soundy@zippie:~$ perl -v
This is perl, v5.6.0 built for i386-linux
Copyright 1987-2000, Larry Wall

Source:
# Connect and bind to the LDAP Database
my $ldap = Net::LDAP->new('delphi.ihug.co.nz') or do {
        print "Couldn't connect to LDAP database $@\n";
        exit 1;
};

if (!$ldap->bind("cn=Manager, $authbase", password => $authpass)) {
        print "Ldap Bind failed!\n";
        exit 1;
}

my $mesg = $ldap->search(
        base => "$authbase",
        filter => '(objectclass=ihugAuthAccount)',


It used the same amount of Ram.


Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: sim...@st...

The real fighting men and women of the 21st century will continue
to be techo's backed up by the grunts with bad haircuts and rifles.

New FAQ is out

[Clif H. <ch...@po...>]

A new faq is out.

Added meta tags to the FAQ html version so that web search
engines could index the FAQ page.

Added a question and answer about ACI/ACL.

Added a URL link to Novell's LDAPzone developers web 
page.

FAQ is available from the Perl-LDAP web page.
 
Regards,

Clif Harden          ch...@po...

Re: [Fwd] Problem with Net::LDAP

[Clif H. <ch...@po...>]

Simon Allard wrote:
> 
> > > This is true, however 95000 * 200 bytes (rough size of the example entry)
> > > only comes to about 18 megabytes, and Simon said his perl process was using
> > > 250 megabytes :-(
> > >
> > > That's a lot of overhead, unless Simon missed a zero out of his entry count
> > > - 950000 entries would work out to use about the observed quantity of
> > > memory. Well, the same order of magnitude anyway.
> >
> > It would be nice to know what version of perl he is running
> > and on what type of systems.
> 
> Output from perl -v
> This is perl, version 5.003 with EMBED
>         built under solaris at Jun 10 1998 02:26:14
>         + suidperl security patch
> 
> The perl is the version that comes with Oracle 9i.
> 
> delphi:~$ uname -a
> SunOS delphi.ihug.co.nz 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-2
> 
> Simon Allard (Senior Tool Monkey)
> IHUG
> Ph (09) 358-5067   Email: sim...@st...
> 
> The real fighting men and women of the 21st century will continue
> to be techo's backed up by the grunts with bad haircuts and rifles.


Simon,

The lowest version of perl that we support is version 5.004.
Very soon we will only support 5.005_03 and above.

IMO your problem is in your version of perl.
 
Regards,

Clif Harden          ch...@po...

Re: [Fwd] Problem with Net::LDAP

[Simon A. <sim...@st...>]

> This is true, however 95000 * 200 bytes (rough size of the example entry)
> only comes to about 18 megabytes, and Simon said his perl process was using
> 250 megabytes :-(
>
> That's a lot of overhead, unless Simon missed a zero out of his entry count
> - 950000 entries would work out to use about the observed quantity of
> memory. Well, the same order of magnitude anyway.

Unfortantly its is only 95000 entrys. I can read exactly the same amount
of data out of our Oracle databae and use ony 20meg of RAM.


Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: sim...@st...

The real fighting men and women of the 21st century will continue
to be techo's backed up by the grunts with bad haircuts and rifles.

Re: [Fwd] Problem with Net::LDAP

[Simon A. <sim...@st...>]

> > This is true, however 95000 * 200 bytes (rough size of the example entry)
> > only comes to about 18 megabytes, and Simon said his perl process was using
> > 250 megabytes :-(
> >
> > That's a lot of overhead, unless Simon missed a zero out of his entry count
> > - 950000 entries would work out to use about the observed quantity of
> > memory. Well, the same order of magnitude anyway.
>
> It would be nice to know what version of perl he is running
> and on what type of systems.

Output from perl -v
This is perl, version 5.003 with EMBED
        built under solaris at Jun 10 1998 02:26:14
        + suidperl security patch

The perl is the version that comes with Oracle 9i.

delphi:~$ uname -a
SunOS delphi.ihug.co.nz 5.6 Generic_105181-20 sun4u sparc SUNW,Ultra-2




Simon Allard (Senior Tool Monkey)
IHUG
Ph (09) 358-5067   Email: sim...@st...

The real fighting men and women of the 21st century will continue
to be techo's backed up by the grunts with bad haircuts and rifles.

Re: [Fwd] Problem with Net::LDAP

[Clif H. <cl...@di...>]

> 
> Graham Barr <gb...@po...> wrote:
> > It is taking so much memory because it is reading all the results into
> > memory before returning for you to process them.
> > 
> > I suspect you don't really need all of the entries, so try modifying your
> > filter to result the resutl set that is being sent.
> > 
> > If this is not possible, try using the callback option. This allows you
> > to process each entry as it arrives from the server.
> > 
> > Graham.
> 
> This is true, however 95000 * 200 bytes (rough size of the example entry)
> only comes to about 18 megabytes, and Simon said his perl process was using
> 250 megabytes :-(
> 
> That's a lot of overhead, unless Simon missed a zero out of his entry count
> - 950000 entries would work out to use about the observed quantity of
> memory. Well, the same order of magnitude anyway.
> 
> Cheers,
> 
> Chris
> 
> 


It would be nice to know what version of perl he is running
and on what type of systems.

Regards,

Clif