other versions
- jessie 3.1.8-1.2+b1
confdb2ldif(8) | System Manager's Manual | confdb2ldif(8) |
NAME¶
confdb2ldif - Create an LDIF file from a cluster configurationSYNOPSIS¶
confdb2ldap <basedn> [<config object base>]DESCRIPTION¶
confdb2ldif reads the cluster configuration from the openais object database and generates an LDIF file suitable for importing into an LDAP database. The LDIF file is written to standard output.OPTIONS¶
- <basedn>
- This is the base DN of the LDAP server into which the configuration will be imported. confdb2ldif will create a "cn=cluster" object below this to contain the cluster configuration. The base DN is usually derived from the host's domain name. So if the host is ldapsrv.mycorp.com then the base DN could be dc=mycorp,dc=com.
- [<config object base>]
- Configuration object in the objdb to start from. This defaults to "cluster" and there should rarely be any need to change it.
COMMENTS¶
confdb2ldif uses the openais libconfdb to read the configuration. The default way to do this is run against a running aisexec to read the live configuration. It is possible to generate an LDIF file from a non-running system by using the standalone feature of openais's libconfdb.OPENAIS_DEFAULT_CONFIG_IFACE=xmlconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=comor to do it from CCS
OPENAIS_DEFAULT_CONFIG_IFACE=ccsconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=comThe LDIF file is written to stdout and so can be saved or piped straight into ldapmodify if required.
EXAMPLE¶
confdb2ldif dc=mycorp,dc=com | ldapmodify -x -a -D"cn=Directory Manager" -c -v -W