Section 8.1.5. Schema Replication in the Admin Guide for both RHDS9 and 10 needs adjustment.

Some information from Nathan Kinder:

>Schema replication takes place at the beginning of any replication session.  The CSN in 99user.ldif is compared between the master and the consumer, and differing schema is sent over if the consumer is behind the master.  Note that the single CSN is for all schema.  We do not have a CSN at the attribute level (nor a changelog) like we do for normal replication.
>
>This check happens at the beginning of every replication session.  A schema update itself will not trigger replication.  We need an actual change in the replicated area that triggers replication for the replication session to start.
>
>You can't enable/disable schema replication, as replication could fail if the consumer doesn't have the schema required for changes that need to be sent.