This file (ldap-faq) contains some commonly encountered problems when
installing and using the UM ldap distribution, along with thier
solutions.  Please try the solutions here before contacting
ldap-support@terminator.rs.itd.umich.edu.

PROBLEM:
	ud reports "socket: Error 0" or some other nonsense when I try
	to run it.

SOLUTION:
	The error message is usually bogus.  It is probably caused
	by ud trying to contact a hostname that does not exist.  Try
	running ud with the -s option, like so:

		ud -s hostname.running.an.ldap.daemon

	If that works, edit the file ud/ud.h and change the #define
	for DEFAULT_SERVER.  While you are there, make sure DEFAULT_BASE
	is set to something that makes sense for your site.  Then
	recompile.

PROBLEM:
	ud returns "unknown attribute type" when I try to find somebody.

SOLUTION:
	This is caused by ud asking for a UM-specific attribute called
	multiLineDescription.  You should either add this line to your
	oidtable.at file:

	multiLineDescription:   umichAttributeType.2    : CaseIgnoreList

	or you can apply the ud.mldescription patch to the ud source.
	This patch is available for anonymous ftp from the host
	terminator.rs.itd.umich.edu in the file
	x500/ldap-patches/ud.mldescription

PROBLEM:
	my ldap server dies when I send it certain substring queries.

SOLUTION:
	This is probably caused by a bug in the ldapd filter handling
	code.  You should apply the ldapd.filter patch to the ldapd
	source.  This patch is available for anonymous ftp from the
	host terminator.rs.itd.umich.edu in the file
	x500/ldap-patches/ldapd.filter