[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: remote searches

--On Saturday, September 07, 2002 9:43 PM -0700 Quanah Gibson-Mount <quanah@Stanford.EDU> wrote:

--On Saturday, September 07, 2002 9:40 PM -0700 Howard Chu
<hyc@symas.com> wrote:

Okay, then I'm completely lost.  ldap.conf exists on the machine which
it is querying (ldap3).  Running a query on ldap3 using the same conf
file works fine.  So why doesn't it work when I'm running the query
from a different machine if it doesn't care where ldap.conf is located?

The ldap.conf file must be readable by the client. Unless you've exported this file by NFS or some other remote filesystem, how do you expect your client on a remote machine to be able to read the file that resides on your server?


After re-reading Kurts note, I configured ldap.conf on the machine
ldapsearch is running from.  Now it all works fine.  So, the long and
short answer is, wherever I run ldapsearch from, it needs a basic
ldap.conf file to read.  Thank you.  And, actually, we do use AFS, so I
can probably hack ldapsearch to read an ldap.conf for us from there.
Thanks for the help. :)

Actually, I really don't need ldap.conf. After twiddling a bit, all I really needed was:

1) A base with ldapsearch (ldapsearch -h ldap3 -b 'dc=stanford,dc=edu') works right.


2) When one of my users who is testing our migration is having problems with queries, I need to make sure they aren't mixing attributes between the old directory system and the new (as in this case).


Quanah Gibson-Mount
Senior Systems Administrator
ITSS/TSS/Computing Systems
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

Attachment: pgp4sE97bW0UG.pgp
Description: PGP signature