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

Re: back-config again

To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: back-config again
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Sun, 4 Apr 2004 20:06:10 +0200
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <6.0.1.1.0.20040404105321.048821a0@127.0.0.1>
References: <6.0.1.1.0.20040328194032.0487ddc0@127.0.0.1> <01c801c41548$0a3a0660$0e01a8c0@CELLO> <6.0.1.1.0.20040328212300.0487c488@127.0.0.1> <4067CE71.3030905@stroeder.com> <6.0.1.1.0.20040329082641.048af728@127.0.0.1> <HBF.20040404ukur@bombur.uio.no> <6.0.1.1.0.20040404095736.04861c78@127.0.0.1> <HBF.20040404ut1p@bombur.uio.no> <6.0.1.1.0.20040404105321.048821a0@127.0.0.1>

Kurt D. Zeilenga writes:
>At 10:41 AM 4/4/2004, Hallvard B Furuseth wrote:
>> One thing I hope will remain fairly easy to do automatically, and to
>> administer, is to build a fresh database "outside" the running slapd,
>> and then take slapd down to replace the database.
> 
> I'd like to be able to do that WITHOUT taking slapd down.

Sure, but that's another issue.  Which is missing from doc/devel/todo, I
now notice.  I don't know how large the project is.

For back-config, it's sufficient not to mess up whatever means slapd
supports to replace the database at the time back-config is implemented.

-- 
Hallvard

References:
- Re: back-config again
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: back-config again
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: back-config again
  - From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Re: back-config again
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>

Prev by Date: Re: back-config again
Next by Date: Re: HEADS UP: disclosing information on failed bind
Index(es):
- Chronological
- Thread