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

Re: problem reading directory with 2.1.17

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: problem reading directory with 2.1.17
From: Ian Macdonald <ian@google.com>
Date: Wed, 9 Apr 2003 10:44:55 -0700
Cc: Ian Macdonald <ian@google.com>, openldap-software@OpenLDAP.org
Content-disposition: inline
In-reply-to: <5.2.0.9.0.20030409101641.02c7b958@127.0.0.1>
Organization: Google, Inc.
References: <002401c2fe50$2c75ed80$0e01a8c0@CELLO> <20030409032739.GL21284@google.com> <002401c2fe50$2c75ed80$0e01a8c0@CELLO> <5.2.0.9.0.20030409101641.02c7b958@127.0.0.1>
User-agent: Mutt/1.4.1i

On Wed 09 Apr 2003 at 10:18:16 -0700, you wrote:

> At 01:36 AM 4/9/2003, Ian Macdonald wrote:
> >I can't find any mention of this in the documentation. 
> 
>    http://www.openldap.org/faq/index.cgi?file=842

I've done this, but as remarkable as it sounds, I still can't read from
the directory. I still get 'No such object' back from it.

Ian
-- 
Ian Macdonald               | Raising pet electric eels is gaining a lot 
System Administrator        | of current popularity. 
Google, Inc.                | 
ian@google.com              | 
+1 650-623-4265             |

References:
- RE: problem reading directory with 2.1.17
  - From: "Howard Chu" <hyc@highlandsun.com>
- Re: problem reading directory with 2.1.17
  - From: Ian Macdonald <ian@google.com>
- Re: problem reading directory with 2.1.17
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: can't compile 2.1.16 on Redhat 9. More info.
Next by Date: Aliases / Secondary Lookups
Index(es):
- Chronological
- Thread