Re: Upgrade from OpenLDAP 2.1.30 -> 2.3.37

[Quanah Gibson-Mount <quanah@zimbra.com>]

--On Tuesday, July 31, 2007 9:43 PM +0100 Gavin Henry 
<ghenry@suretecsystems.com> wrote:

> Quanah Gibson-Mount wrote:
> > --On Tuesday, July 31, 2007 8:34 AM -0700 Quanah Gibson-Mount
> > <quanah@zimbra.com> wrote:
> >
> > > --On Tuesday, July 31, 2007 11:09 AM -0400 Aaron Richton
> > > <richton@nbcs.rutgers.edu> wrote:
> > >
> > > > > eq and sub), so I don't see a problem there. I still have to look a
> > > > > bit more into DB_CONFIG tuning, but still, is it normal behaviour of
> > > >
> > > > After modifying DB_CONFIG -- and perhaps you already have made
> > > > intermediate edits -- make sure to stop slapd and run db_recover.
> > >
> > >
> > > Why?  If DB_CONFIG changes, slapd will automatically re-initialize the
> > > DB environment.
> >
> > [on a restart].  I.e., stopping slapd and then starting it is
> > sufficient. There is no need to run db_recover.
>
> You don't need a restart if setting via cn=config

Eh, yes, you do.  slapd does not (and cannot) modify the BDB environment 
set by DB_CONFIG while it is running.  Which is what this discussion is 
about.  You are correct that you don't have to restart slapd to make 
changes to the entry cache setting or idlcachesetting (both in slapd.conf) 
via cn=config.

--Quanah

--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration