For Programmers: Free Programming Magazines  


Home > Archive > LDAP > February 2007 > schema->dump returns nothing









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author schema->dump returns nothing
Eric Nichols

2007-02-26, 7:22 pm

I've upgraded to .34 of perl-ldap and I tried to dump the schema of an Active
Directory Global Catalog. All that shows is about 20 lines of carriage
returns.

All other functions seem to work fine.
Help?

Peter Marschall

2007-02-27, 7:24 pm

Hi,

On Monday, 26. February 2007 15:34, Eric Nichols wrote:
> I've upgraded to .34 of perl-ldap and I tried to dump the schema of an
> Active Directory Global Catalog. All that shows is about 20 lines of
> carriage returns.
>
> All other functions seem to work fine.
> Help?

Switch to an LDAP server conforming to the RFCs ;-)

No, let's get serious:
AD does not adhere to the LDAP standards for publishing schema information.

Although there has work been gone into perl-ldap to make some/most of the
schema fucntions work with AD to, I guess dump() relies on the standard.

Regards
Peter
--
Peter Marschall
peter@adpm.de
Graham Barr

2007-02-27, 7:24 pm

On Feb 27, 2007, at 3:40 PM, Peter Marschall wrote:
> On Monday, 26. February 2007 15:34, Eric Nichols wrote:
[color=darkred]
> Although there has work been gone into perl-ldap to make some/most
> of the
> schema fucntions work with AD to, I guess dump() relies on the
> standard.


I should not matter. ::Schema, after successful parse, remembers the
entry and dump just does an LDIF dump on that entry.

So the question is, was the parse successful ?

I guess some digging around inside of $schema is in order to see what
is there. And if there is no entry stored I guess we need to
determine why.

Graham.

Eric Nichols

2007-02-27, 10:21 pm

On Tue, February 27, 2007 7:51 pm, Graham Barr wrote:
> On Feb 27, 2007, at 3:40 PM, Peter Marschall wrote:
>
>
> I should not matter. ::Schema, after successful parse, remembers the
> entry and dump just does an LDIF dump on that entry.
>
> So the question is, was the parse successful ?
>
> I guess some digging around inside of $schema is in order to see what
> is there. And if there is no entry stored I guess we need to
> determine why.
>
> Graham.
>


I did a cursory check and was able to dump an attribute (sn) so the data is
there. I made a work around and was able to use Storable to get it to a file.
The save/restore is remarkably fast. Graham, I can send over the storable
blob which will give you my schema object I generated.

Graham Barr

2007-02-27, 10:21 pm

It is a bug in Net::LDAP::LDIF, try

http://svn.goingon.net/repos/perl-l...et/LDAP/LDIF.pm

Or you can workaround with

$fh = \*STDOUT;
Net::LDAP::LDIF->new($fh,"w", wrap => 999_999_999)->write($schema-
>entry);



Graham.

On Feb 27, 2007, at 7:29 PM, Eric Nichols wrote:

> On Tue, February 27, 2007 7:51 pm, Graham Barr wrote:
>
> I did a cursory check and was able to dump an attribute (sn) so the
> data is
> there. I made a work around and was able to use Storable to get it
> to a file.
> The save/restore is remarkably fast. Graham, I can send over the
> storable
> blob which will give you my schema object I generated.
>


Eric Nichols

2007-02-28, 8:17 am

That seems to have licked the problem! I'm getting a real dump now...

Many thanks for the fast help..

On Tue, February 27, 2007 9:29 pm, Graham Barr wrote:
> It is a bug in Net::LDAP::LDIF, try
>
> http://svn.goingon.net/repos/perl-l...et/LDAP/LDIF.pm
>
> Or you can workaround with
>
> $fh = \*STDOUT;
> Net::LDAP::LDIF->new($fh,"w", wrap => 999_999_999)->write($schema-
>
>
> Graham.
>



Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com