[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: ldapsearch
You might want to run ldapsearch under truss to see what it's doing.
Specifically, make sure it's opening the ldap.conf file at the location you
expect.
I'm glad to see our packaged binaries worked for you. FYI- we just released
a new version of CNS, our bundled versions of pam_ldap and nss_ldap.
Matthew Hardin
Symas Corporation
Packaged, certified, and supported LDAP software:
http://www.symas.net/download
> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Lopez, Damien
> Sent: Wednesday, September 03, 2003 2:58 PM
> To: openldap-software@OpenLDAP.org
> Subject: RE: ldapsearch
>
>
> The weird thing it does is one you run ldapsearch with the host
> specified on
> the command line it works fine but if it needs to get the
> information out of
> ldap.conf it returns no such object. I have installed the
> pre-compiled symas
> pkgs on this machine and there version of ldapsearch has no
> issues but when
> I compile it myself I get that error. We have a third party app that also
> core dumps and I think they might be related. My guess is openldap is not
> getting installed correctly. The third party app and ldapsearch
> our the only
> things not completely working. Solaris authentication and other
> apps have no
> issues.
>
>
>
>
>
> -----Original Message-----
> From: Alan Sparks [mailto:asparks@doublesparks.net]
> Sent: Wednesday, September 03, 2003 7:14 AM
> To: Damien_Lopez@intuit.com
> Cc: openldap-software@OpenLDAP.org
> Subject: Re: ldapsearch
>
>
> Lopez, Damien said:
> > Does ldapsearch need to be linked against libldap and liblber for it
> > to work correctly? The machine I am working on does not and I am having
> > some issues with ldapsearch.
>
> It won't, but ldd only shows the libraries if they are dynamically linked.
> If somehow you convinced it to link static, or it somehow found static
> libraries to link against, it won't show. If it's the wrong libraries by
> some wierd ituation, you'd have problems.
>
> Perhaps it is not a library problem. If you could be more specific as to
> what is going wrong, maybe that would help.
> -Alan
>
> ===========
> Alan Sparks, UNIX/Linux Systems Administrator
> <asparks@doublesparks.net>
>
>
>
>