It should be acceptable as an LDIF as input to slapadd. If it is not, it is buggy by definition. Remember, we should be able to perform database configuration OFF-LINE. ie. without slapd running. And obviously when off-line, slapadd works whereas ldapmodify, ldapadd etc. cannot.
If you would spend the time to start with a basic cn=config setup, and then perform the ldap modifications as noted in the admin guide, your end result would be a cn=config DB you could *slapcat* into LDIF, which you could then use as a template for loading other servers. In fact, you'd be long done with this if you'd simply done that very simple thing.
Just because slapadd doesn't parse LDIF meant for ldap modify does *not* mean it is buggy. It means you are following the admin guide.
The admin guide is not a document that explains how to do anything and everything under the sun. It is a general guide that gives working examples of how to do various things. The end user is supposed to have enough understanding and general competence to be able to extrapolate how to go from there.
In addition, you've also been pointed to test suites that set up multi-master replication of cn=config. You could have trivially exported those cn=config DB's via slapcat as well.
You seem awfully determined to have other people take the time to do your work for you, rather than doing what you could have already done weeks ago in a few minutes.
--Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration