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

Re: OpenLDAP setup

> Hugo.van.der.Kooij@caiw.nl wrote:
> > On Tue, 7 Nov 2000, Daniel Tiefnig wrote:
> >
> > > Hugo.van.der.Kooij@caiw.nl wrote:
> > >
> > > > You must use ldapadd or slapadd where ldapadd is prefered because you can
> > > > work on an operational server where it is ill advised to use slapadd while
> > > > someone is using the LDAP server. You will find that slapadd is the
> > > > closest thing there is to a replacement of ldif2ldm.
> > >
> > > but when i use slapadd to add entries to my current DB, i've to restart slapd
> > > afterwards to make changes taking effekt. is there a way to avoid this?
> >
> > use ldapadd!
> hehehe.... that's what i thought too...
> i just asked, because u said: '... it is still advised to use slapadd while
> someone is using the LDAP server...'. i was just wondering why, and how... did i
> get u wrong with that?

You must not be running slapd when you run slapadd.  Slapadd modifies the
database and index files without regard to what slapd is doing, ie. there
is no provision for cooperation between the two (nor should there be).
Slapd, when it is running expects to have exclusive access to the database

For this reason, many people suggest and encourage using ldapadd.  However,
if preserving operational attributes is important to you, such as
createtimestamp, modifytimestamp, creatorsname, and modifiersname, then
you must use slapadd.  A workaround would be to temporarily configure
your server as a slave, and bind as the updatedn, so that the server will
accept those attributes from slapadd.