At 02:29 PM 5/17/2006, Chris Ridd wrote: >On 17/5/06 9:32, Anthony M. Martinez <[EMAIL PROTECTED]> wrote: > >> Is there a way to get Net::LDAP to use the system configuration file to >> get the hostnames to connect to? Passing "", undef, or nothing to >> Net::LDAP->new doesn't seem to do anything other than fail. I could >> always open the configuration files, but that is slightly painful, given >> that the first of the vagaries is that it could be /etc/ldap.conf >> (fedora), /usr/local/etc/ldap.conf (fBSD), or /etc/ldap/ldap.conf >> (debian). > >Those are the config files for a certain set of LDAP libraries.
and/or a certain set of LDAP client programs (e.g., PAM/LDAP, NSS/LDAP). >Net::LDAP >does not use those libraries, nor any other LDAP libraries, and it would be >inappropriate to try to parse them IMHO. I concur. I regret choosing an implicit defaulting mechanism (e.g., one which the client programs have little control over) for OpenLDAP client libraries. Providing (or using an existing general purpose) explicit defaulting mechanism (e.g., one which the client programs have full control over) outside of the client library would have been, in my opinion, a much better choice. But I digress... Regards, Kurt
