Andrej,
I normally use the client commands and store the ouptut into an array for
processing. with the NET::LDAP it seems too much typing. :-) I should have
mentioned in my initial email that I have read through the FAQ's and articles
on NET::LDAP. I didn't see too much that I can do with the module that I am
currently not doing. But I think it is because I haven't used it yet.
Thanks for your input. I will definetly give it a shot. :-)
Andrej Ricnik-Bay <[EMAIL PROTECTED]> wrote: On 3/7/07, Bill wrote:
> Hi All.
Hi Bill!
> I am new to this email group. I been reading the emails for
> the past couple of weeks and notice mostly everyone is using
> Net::LDAP module for perl to ldap interaction. Normally we have
> ibm ldap client on our server installed, thus can issue the commands
> directly from the OS.
That'll be because this is the prel-ldap list, not a generic
ldap one ... :} ... and using ldapsearch/ldapmodify with system()
would be cumbersome and error-prone. Net::LDAP works a treat
for these tasks, and I'd hate not to have it. Not that I'm much of
a perl-guru - I don't use it often enough to be highly proficient.
> I am contemplating couple of this: (1) advantages and disadvantages
> of Net::LDAP modules vs command line client,
Well ... I use the openldap client tools to query and modify
eDir on a one-off basis, too; I use Net::LDAP for CGI programs (e.g.
exporting of directory information to CSV) or more complex programmatic
tasks (like consolidation between eDir and other data sources).
> (2) I want to contribute to this list and help anyone I can, but it seems
> like everyone is using this module and I have not used. I suppose after
> I have the answer to question 1 then I can better help.
Quite possible.
> Thanks - Bill
Cheers,
Andrej
---------------------------------
Looking for earth-friendly autos?
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
