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

RE: ldapi:/// Unix & domain socket usage

This works great if I use the ldapsearch binary from Openldap with -H.
However, if I seem to have problems with the Mozilla 4.x SDK.  Writing a
sample client, I can search ldap:/// with no problem.  If I then try
ldapi:/// I get ldap_search_ext: Bad parameter to an ldap routine.

-----Original Message-----
From: owner-openldap-devel@OpenLDAP.org
[mailto:owner-openldap-devel@OpenLDAP.org]On Behalf Of Ben Collins
Sent: Tuesday, July 03, 2001 4:30 PM
To: Eric T. Blue
Cc: Kurt D. Zeilenga; openldap-devel@OpenLDAP.org
Subject: Re: ldapi:/// Unix & domain socket usage

On Tue, Jul 03, 2001 at 04:21:51PM -0400, Eric T. Blue wrote:
> Hmmm... this is really strange.  Whenever I was looking at this earlier
> today, the path abolutely was /tmp/389.  Now, after  a few reconfigures,
> path is in fact /tmp/.ldapi_sock.

Perhaps you accidently told it to listen to ldapi://389/? (forgot what
this code looks like, but that might change the file used for the

> Regarding Ben's reply: Then, is there nothing else special that is
> Does searching via a URL just provide a layer of abstraction to the

Yes, the library decodes the URI, same for ldaps:// URI's.


/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '