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

Re: [Q] what is the best practice or right way to change schemas order for cn=config case?

To: Zeus Panchenko <zeus@ibs.dn.ua>
Subject: Re: [Q] what is the best practice or right way to change schemas order for cn=config case?
From: Christian Kratzer <ck-lists@cksoft.de>
Date: Thu, 21 Dec 2017 17:18:18 +0100 (CET)
Cc: openldap-technical@openldap.org
In-reply-to: <20171220190723.92865@relay.xx>
References: <20171220190723.92865@relay.xx>
User-agent: Alpine 2.21 (BSF 202 2017-01-01)

Hi,

On Wed, 20 Dec 2017, Zeus Panchenko wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi,

what is the best practice or right way to change schemas order for cn=config case?

1. to move file?
2. to ldapmodify?

for the one used to slapd.conf both of ways look weird ... :(


for those cases that ldapmodify that does not work you can use slapcat
to dump all of the cn=config database edit it and reimport using slapadd.

Adding -n0 to slapadd and slapcat makes it use the cn=config database.

Greetings
Christian

--
Christian Kratzer                   CK Software GmbH
Email:   ck@cksoft.de               Wildberger Weg 24/2
Phone:   +49 7032 893 997 - 0       D-71126 Gaeufelden
Fax:     +49 7032 893 997 - 9       HRB 245288, Amtsgericht Stuttgart
Mobile:  +49 171 1947 843           Geschaeftsfuehrer: Christian Kratzer
Web:     http://www.cksoft.de/

Follow-Ups:
- Re: [Q] what is the best practice or right way to change schemas order for cn=config case?
  - From: "Zeus Panchenko" <zeus@ibs.dn.ua>

References:
- [Q] what is the best practice or right way to change schemas order for cn=config case?
  - From: "Zeus Panchenko" <zeus@ibs.dn.ua>

Prev by Date: OpenLDAP slave failure in case of master indisponibility
Next by Date: Re: [Q] what is the best practice or right way to change schemas order for cn=config case?
Index(es):
- Chronological
- Thread