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

Re: (ITS#4504) ldapsearch output incorrect

--On Tuesday, April 25, 2006 9:17 PM +0000 Kurt@OpenLDAP.org wrote:

> At 12:37 PM 4/25/2006, quanah@OpenLDAP.org wrote:
>> Full_Name: Quanah Gibson-Mount
>> Version: 2.3.21
>> OS: NA
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (
>> When a system "ldap.conf" file exists, or a user ".ldaprc" file exists,
>> and it specifies the default BASE to be used, the ldapsearch output does
>> not show that that base is being used.  Instead, it says it is using a
>> base of <>, which is obviously incorrect.
> It works as intended.  <> indicates the default base,
> if specified, is used.  Otherwise, <> is used.

So what you are saying is:

(a) If the default base is set in ldap.conf or .ldaprc, <> is used.
(b) If no base is specified, <> is used
(c) if -b is used, that base is used.

So, my question is, why doesn't case (a) behave like case (c).  It seems 
very nonsensical to me for case (a) to behave the same as case (b).  The 
current behavior leads to output like:

# extended LDIF
# LDAPv3
# base <> with scope subtree
# filter: uid=quanah
# requesting: ALL

This means, then, that the extended output is incorrect and misleading. 
The base is not <>, it is cn=people,dc=stanford,dc=edu, in this case.  This 
makes telling whether or not ldapsearch is behaving as intended rather 
obnoxious to deduce (although -d -1 certainly has it in the output).


Quanah Gibson-Mount
QA Engineer