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

Re: ppolicy and rwm/relay segfaulting

To: Tim Watts <tw@dionic.net>
Subject: Re: ppolicy and rwm/relay segfaulting
From: Gregory Haverkamp <gahaverkamp@lbl.gov>
Date: Tue, 4 Dec 2012 14:02:49 -0800
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
In-reply-to: <50BE6D99.4030208@dionic.net>
References: <50BE6D99.4030208@dionic.net>

In my base, it was back-relay. back-ldap fixed the back-relay problem (with a performance degradation), but then I encountered oodles of problems with back-ldap, followed by back-meta, after which I was forced to scrap any hope of maintaining my legacy naming context without synchronization.

I started a bug report on one of them, but I was in the middle of a roll-out of the new directory infrastructure, and I never got back to all three problems.

Greg

On Tue, Dec 4, 2012 at 1:39 PM, Tim Watts <tw@dionic.net> wrote:

This is weird - quite possible a config problem, I'm hoping someone can spot it :)

I have a minimal slapd server which works fine with either an rwm/relay section or a ppolicy section - but not both at once.

I'm happy to explain *why* I need to do this if asked, but for now it would just clutter this message. I do have a Really Good(TM) reason.

Follow-Ups:
- Re: ppolicy and rwm/relay segfaulting
  - From: Tim Watts <tw@dionic.net>

References:
- ppolicy and rwm/relay segfaulting
  - From: Tim Watts <tw@dionic.net>

Prev by Date: ppolicy and rwm/relay segfaulting
Next by Date: Re: ppolicy and rwm/relay segfaulting
Index(es):
- Chronological
- Thread