9:07 a.m.
-----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 ... :(
- --
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
-----BEGIN PGP SIGNATURE-----
iEYEARECAAYFAlo6mMsACgkQr3jpPg/3oypRzwCdHNMNgUewiolW91I7DB7cK5dE
BqoAn0tXLDIMIBg0W9uG39pwN7LPRPth
=jKuI
-----END PGP SIGNATURE-----
8:18 a.m.
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(a)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/
9:14 a.m.
Christian Kratzer <ck-lists(a)cksoft.de> wrote:
> 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.
it is one of the causes making me to delay the switch to cn=config
topology ... :(
all scenarios described looks too artificial ... since the very
elementary and simple operation (editing config file) becames a pain ...
especially when I need to reorder schema files on many hosts ...
I was sure I'm missing something in how to handle such a tasks ...
--
Zeus V. Panchenko jid:zeus@im.ibs.dn.ua
IT Dpt., I.B.S. LLC GMT+2 (EET)
8:15 a.m.
Le jeudi 21 décembre 2017, 19:14:13 CET Zeus Panchenko a écrit :
it is one of the causes making me to delay the switch to cn=config
topology ... :(
all scenarios described looks too artificial ... since the very
elementary and simple operation (editing config file) becames a pain ...
especially when I need to reorder schema files on many hosts ...
I was sure I'm missing something in how to handle such a tasks ...
Hello,
We have a tool to help with this called ldap-schema-manager. It does not have its own repo
yet you can find it here: https://gitlab.fusiondirectory.org/fusiondirectory/schema2ldif
It does not have a reorder feature yet but it’s the kind of things that could be added. It
supports insertion, update, listing and erasing (emptying - removal support should be
added now that openldap supports it).
Côme
1899
days inactive
1919
days old
openldap-technical@openldap.org
3 comments
3 participants
participants (3)
-
Christian Kratzer -
Côme Chilliet -
Zeus Panchenko