Hi Andrey,
This is definitely a good idea, and I will work on it when I get a
chance. I think we might add this script to the product - maybe. If
that's the case, there will probably more changes as well. So, this
isn't the final version by any means.
Thanks,
Mark
On 02/07/2012 12:35 PM, Andrey Ivanov wrote:
Hi Mark,
nice tool. It seems you have hardcoded into the script some default
values like config entries in cn=config suffix. Is there a way to do
it in a more flexible way. For example, dseconv could take (some)
default values from template-dse.ldif, template-*.ldif and if they are
not found in the templates just failover to the hardcoded values?
It will save some time on the script maintenance when the default
values are changed and/or added in the templates.
@+
2012/2/6 Mark Reynolds <marey...@redhat.com <mailto:marey...@redhat.com>>
Hi All,
This was a side project of mine for some time, and I just ported
it to DS 389. It basically parses the dse.ldif into a readable
format. It groups all the backend info together. So each backend
lists its own indexes, config, replication info, etc. It checks
for non default config settings as well.
It's basically a great way to take a quick look at a customers config:
--
389-devel mailing list
389-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
--
389-devel mailing list
389-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
