Hi Rich,
Rich Megginson <rmeggins(a)redhat.com>
> On RH documentation I read to:
> - upgrade all masters;
> - then upgrade slaves;
> - lately restart.
Yes. This is the recommended procedure.
> This approach seems to lead to some service discontinuity, as - during
> this migration - I should stop writes to all master/slaves.
Why?
To avoid discontinuity, I should do a rolling restart, right?
Rolling restart means I have a small time frame T0 where schemas are different
between nodes.
If during T0 a write is replicated between NodeB and NodeA, I suppose
replication will fail due to mismatching schema, right?
> I found a possible typo here:
>
http://directory.fedoraproject.org/wiki/Dynamically_Reload_Schema
Yes. I have fixed the wiki ... attributetypes, objectclasses,
matchingrules, are
now operational
is there a way to tell 389 to print all operational attributes?
Thx + Peace,
R:
--
Roberto Polli
Community Manager
Babel S.r.l. -
http://www.babel.it
T: +39.06.9826.9651 M: +39.340.652.2736 F: +39.06.9826.9680
P.zza S.Benedetto da Norcia, 33 - 00040 Pomezia (Roma)
CONFIDENZIALE: Questo messaggio ed i suoi allegati sono di carattere
confidenziale per i destinatari in indirizzo.
E' vietato l'inoltro non autorizzato a destinatari diversi da quelli indicati
nel messaggio originale.
Se ricevuto per errore, l'uso del contenuto e' proibito; si prega di
comunicarlo al mittente e cancellarlo immediatamente.