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

2018-01-09 Thread Côme Chilliet
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 ... >

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

2017-12-21 Thread Zeus Panchenko
Christian Kratzer 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

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

2017-12-21 Thread Howard Chu
Christian Kratzer wrote: 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? Use ldapmodrdn. 1. to move file? 2. to ldapmodify? for the one used to

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

2017-12-21 Thread Christian Kratzer
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

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

2017-12-20 Thread Zeus Panchenko
-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