confdb2ldif(8) [debian man page]
confdb2ldif(8) System Manager's Manual confdb2ldif(8) NAME
confdb2ldif - Create an LDIF file from a cluster configuration SYNOPSIS
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 lib- confdb. eg to read the configuration from /etc/cluster/cluster.conf, use the following command: OPENAIS_DEFAULT_CONFIG_IFACE=xmlconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com or to do it from CCS OPENAIS_DEFAULT_CONFIG_IFACE=ccsconfig:cmanpreconfig confdb2ldif dc=mycompany,dc=com The LDIF file is written to stdout and so can be saved or piped straight into ldapmodify if required. It's important that the 99cluster.ldif schema file has been loaded into the LDAP server before adding the contents of this generated LDIF file. EXAMPLE
confdb2ldif dc=mycorp,dc=com | ldapmodify -x -a -D"cn=Directory Manager" -c -v -W BUGS
confdb2ldif parses the cluster configuration without checking it against the loaded schema. So if there are attributes in the config file that are not known to the schema, parts of the load will fail. It is important to check the results of feeding the output into ldapmodify. In particular aisexec logging operations will not convert into LDIF because they rely on duplicate keys. SEE ALSO
libconfdb(3), openais(8), cluster.conf(5) confdb2ldif(8)
Check Out this Related Man Page
SLAPADD(8) System Manager's Manual SLAPADD(8) NAME
slapadd - Add entries to a SLAPD database SYNOPSIS
/usr/sbin/slapadd [-b suffix] [-c] [-d debug-level] [-f slapd.conf] [-F confdir] [-g] [-j lineno] [-l ldif-file] [-n dbnum] [-o option[=value]] [-q] [-s] [-S SID] [-u] [-v] [-w] DESCRIPTION
Slapadd is used to add entries specified in LDAP Directory Interchange Format (LDIF) to a slapd(8) database. It opens the given database determined by the database number or suffix and adds entries corresponding to the provided LDIF to the database. Databases configured as subordinate of this one are also updated, unless -g is specified. The LDIF input is read from standard input or the specified file. All files eventually created by slapadd will belong to the identity slapadd is run as, so make sure you either run slapadd with the same identity slapd(8) will be run as (see option -u in slapd(8)), or change file ownership before running slapd(8). Note: slapadd will also perform the relevant indexing whilst adding the database if any are configured. For specfic details, please see slapindex(8). OPTIONS
-b suffix Use the specified suffix to determine which database to add entries to. The -b cannot be used in conjunction with the -n option. -c enable continue (ignore errors) mode. -d debug-level enable debugging messages as defined by the specified debug-level; see slapd(8) for details. -f slapd.conf specify an alternative slapd.conf(5) file. -F confdir specify a config directory. If both -f and -F are specified, the config file will be read and converted to config directory format and written to the specified directory. If neither option is specified, an attempt to read the default config directory will be made before trying to use the default config file. If a valid config directory exists then the default config file is ignored. If dry-run mode is also specified, no conversion will occur. -g disable subordinate gluing. Only the specified database will be processed, and not its glued subordinates (if any). -j lineno Jump to the specified line number in the LDIF file before processing any entries. This allows a load that was aborted due to errors in the input LDIF to be resumed after the errors are corrected. -l ldif-file Read LDIF from the specified file instead of standard input. -n dbnum Add entries to the dbnum-th database listed in the configuration file. The -n cannot be used in conjunction with the -b option. To populate the config database slapd-config(5), use -n 0 as it is always the first database. It must physically exist on the filesys- tem prior to this, however. -o option[=value] Specify an option with a(n optional) value. Possible generic options/values are: syslog=<subsystems> (see `-s' in slapd(8)) syslog-level=<level> (see `-S' in slapd(8)) syslog-user=<user> (see `-l' in slapd(8)) schema-check={yes|no} value-check={yes|no} The schema-check option toggles schema checking (default on); the value-check option toggles value checking (default off). The latter is incompatible with -q. -q enable quick (fewer integrity checks) mode. Does fewer consistency checks on the input data, and no consistency checks when writing the database. Improves the load time but if any errors or interruptions occur the resulting database will be unusable. -s disable schema checking. This option is intended to be used when loading databases containing special objects, such as fractional objects on a partial replica. Loading normal objects which do not conform to schema may result in unexpected and ill behavior. -S SID Server ID to use in generated entryCSN. Also used for contextCSN if -w is set as well. Defaults to 0. -u enable dry-run (don't write to backend) mode. -v enable verbose mode. -w write syncrepl context information. After all entries are added, the contextCSN will be updated with the greatest CSN in the database. LIMITATIONS
Your slapd(8) should not be running when you do this to ensure consistency of the database. slapadd may not provide naming or schema checks. It is advisable to use ldapadd(1) when adding new entries into an existing directory. EXAMPLES
To import the entries specified in file ldif into your slapd(8) database give the command: /usr/sbin/slapadd -l ldif SEE ALSO
ldap(3), ldif(5), slapcat(8), slapindex(8), ldapadd(1), slapd(8) "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/) ACKNOWLEDGEMENTS
OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>. OpenLDAP Software is derived from Uni- versity of Michigan LDAP 3.3 Release. OpenLDAP 2012/04/23 SLAPADD(8)