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

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

Hmmm... this is really strange.  Whenever I was looking at this earlier
today, the path abolutely was /tmp/389.  Now, after  a few reconfigures, the
path is in fact /tmp/.ldapi_sock.

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

Any opinions on IPC over CLDAP?

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

At 12:53 PM 7/3/2001, Ben Collins wrote:
>On Tue, Jul 03, 2001 at 03:35:38PM -0400, Eric T. Blue wrote:
>> I've configured the 2.0.11 dist with --enable-local for LDAP_PF_LOCAL
>> support.  I've also added a listener for ldapi:///, and on startup a
>> pipe is created under /tmp/389.

That seems a bit odd. IIRC, socket should be named /tmp/.ldapi_sock.

>My question is: How do you use this?  Is
>> there some sample code for using this, or any special considerations?  I
>> originally had been doing some research on CLDAP and came across this
>> previous posts.  Is there any special advantage to this implementation
>> CLDAP?  I understand there should be much less protocol overhead, but the
>> limitation is that the client must be on the same host as the LDAP
>You use it by telling the client to connect to "ldapi:///"
> -----------=======-=-======-=========-----------=====------------=-=------
>/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux
>`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com
> `---=========------=======-------------=-=-----=-===-======-------=--=---'