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

Re: monitor backend ruins operational attributes search?

To: OpenLDAP software list <openldap-software@OpenLDAP.org>
Subject: Re: monitor backend ruins operational attributes search?
From: Andreas Hasenack <andreas@conectiva.com.br>
Date: Thu, 3 Feb 2005 19:33:52 -0200
Content-disposition: inline
In-reply-to: <821460CDA7E701A9E2FFB1F8@[10.0.0.1]>
References: <20050203122708.GC22027@conectiva.com.br> <821460CDA7E701A9E2FFB1F8@[10.0.0.1]>
User-agent: Mutt/1.5.6i

On Thu, Feb 03, 2005 at 12:58:18PM -0800, Quanah Gibson-Mount wrote:
> --On Thursday, February 03, 2005 10:27 AM -0200 Andreas Hasenack 
> <andreas@conectiva.com.br> wrote:
> 
> >database monitor
> >access to dn.subtree="cn=Monitor"
> >        by * read
> 
> Make this your *last* database definition and see if it works better.

Then everything seems to work ('-s base -b "" +' and '-b "cn=monitor"').

References:
- monitor backend ruins operational attributes search?
  - From: Andreas Hasenack <andreas@conectiva.com.br>
- Re: monitor backend ruins operational attributes search?
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: Re: 2.2.23's slapd segfaults when using ldapsearch
Next by Date: Re: 2.2.23's slapd segfaults when using ldapsearch
Index(es):
- Chronological
- Thread