I've seen several references on the web to setting up the LDAP SAM to
communicate with the LDAP server via ldapi (IPC) verses ldap (IP).  This
should theoretically much faster.  

My LDAP master is on the same host as the Samba PDC.  With nss_ldap
using "uri ldap://localhost"; and Samba using "ldapsam:ldap://localhost/";
everything works.

But changing nss_ldap to use "uri ldapi://%2fvar%2frun%2fldapi/" breaks
Samba.  Commands like "ls", "finger", and "id" continue to be able to
identify users, but Samba starts reporting "no such user" errors.

Leaving nss_ldap using "ldap://localhost/"; and changing ldapsam to be
"ldapi://%2fvar%2frun%2fldapi" also breaks Samba.

Of course, having both NSS and Samba use ldapi doesn't work either.

Exceuting "ldapsearch -H ldapi://%2fvar%2frun%2fldapi/ uid=adam" works,
so I don't suspect a problem with the ldapi protocol/socket itself.

Is there known bugs/problems with Samba using ldapi? (This is samba
3.0.2).

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Reply via email to