Are you running RHDS8? It is quite old... I'd recommend the latest
version which is RHDS 10.
We are running 9.2 in production at my work place, and I run latest
stable from git personally.
https://access.redhat.com/documentation/en
-US/Red_Hat_Directory_Server/10/html/Configuration_Command_and_File_R
eference/index.html
Yep, this lists the differences nicely. I believe the 9.2 docs still
had this issue, so I'll be sure to read the 10 docs.
> Because it's under the retro_changelog_plugin section, and
the
> discussions of retro changelog is described as:
>
> "T he Retro Changelog plug-in configures Directory Server to
> maintain a
> changelog that is compatible with
> the changelog implemented in Directory Server 4.0, 4.1, and 4.1x.
> Maintaining a retro changelog is
> essential to maintain a changelog for directory clients that depend
> on
> a Directory Server 4.x-style
> changelog."
>
> In the administration guide.
Retro changelog is a separate plug-in. Despite of the name "retro",
it
is still useful to store the change logs in the database independent
from new/old replications.
dn: cn=Retro Changelog Plugin,cn=plugins,cn=config
objectClass: top
objectClass: nsSlapdPlugin
objectClass: extensibleObject
cn: Retro Changelog Plugin
nsslapd-pluginPath: libretrocl-plugin
nsslapd-pluginInitfunc: retrocl_plugin_init
nsslapd-pluginType: object
nsslapd-pluginbetxn: on
nsslapd-pluginEnabled: off
nsslapd-pluginprecedence: 25
nsslapd-plugin-depends-on-type: database
nsslapd-plugin-depends-on-named: Class of Service
cn=changelog5,cn=config is the changelog being used in MMR --
cn=Multimaster Replication Plugin,cn=plugins,cn=config.
Makes sense. Thanks for your time again.
--
William <william(a)firstyear.id.au>