Re: Deleting overlays from cn=config

[Ralf Haferkamp <rhafer@suse.de>]

On Donnerstag, 5. Juni 2008, Howard Chu wrote:
> Ralf Haferkamp wrote:
> > Hi,
> >
> > as back-config does currently not have support for the delete
> > operation (config_back_delete() just returns 
> > LDAP_UNWILLING_TO_PERFORM currently) I am trying to figure out what
> > is needed to get at least delete support for simple overlays (e.g.
> > ppolicy or memberof) running.
>
> Very brave of you. ;)
:) Let's see how far I can get.

[..]
> > I am a bit unsure about the db_destroy() part. Is that enough or is
> > it needed to call the db_close() hooks (when provided by the
> > overlay) before calling db_destroy()? Did I miss something else? Is
> > anybody else currently working on this?
>
> You should call the db_close() hook first.
>
> > Up to now I am testing this only with some simpler overlays
> > (memberof, pcache), I assume that deleting overlays that
> > instantiate their own databases (like pcache, translucent(?)) might
> > get a little more hairy.
>
> Right. We need to distinguish between tearing down due to a normal
> shutdown, which should leave underlying data intact, and tearing down
> due to removal...
Yes, we probably need to add a flag to the db_destroy hooks to indicate 
the difference. Or add an additional hook for the remove-case.

-- 
Ralf