Re: (ITS#4504) ldapsearch output incorrect

[Kurt@OpenLDAP.org]

At 02:36 PM 4/25/2006, quanah@OpenLDAP.org wrote:


>--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) (15.227.137.69)
>>>
>>>
>>> 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.

I don't believe that's what I'm saying.

ldapsearch(1) prints what it provides as input to
ldap_search_ext(3).  The defaulting is not part of
ldapsearch(1) but part of ldap_search_ext(3).

Note that I am only pointing out the intended behavior.
I don't mind treating your report as a request for a
feature enhancement.  I would add that in doing so,
it would be nice to distinguish whether the base
used was user-provided (e.g., command line) or
library provided (e.g., ldap.conf(5)).

Kurt