The following text is a section of the version of the OpenLDAP
Administrator's Guide distribution in the "doc" subpackage of the
Mageia OpenLDAP packages, which is included here for reference.

Please install the openldap-doc package to access the full
Administrator guide, which should be available in
/usr/share/doc/openldap-guide/guide.html

.1. Notes for Mageia users
--------------------------

If you are reading this version of the OpenLDAP Administrator's Guide,
it means you have installed the Mageia OpenLDAP documentation package.

.1.1. File locations
--------------------

The Mageia packages install OpenLDAP with a prefix of /usr, so the
daemons are availble in /usr/sbin, client utilities in /usr/bin,
configuration files under /etc/openldap, libraries in /usr/lib (or
/usr/lib64 on 64bit platforms), and plugins for slapd under
/usr/lib/openldap. The packages are built with all useable backends
and overlays (many as loadable modules), so it should normally not be
necessary to build from source.

The OpenLDAP test suite that is shipped with the source code is also
shipped, ready-to-run, in the openldap-tests package. To run the test
suite (to confirm that all tests passed, investigate some of the
example configurations that are shipped, etc.), simply install
openldap-tests (with urpmi openldap-tests) then (as any user):

     cd /usr/share/openldap/tests

     make tests

.1.2. Upgrading between major versions of OpenLDAP when upgrading the distribution
----------------------------------------------------------------------------------

Upgrades between major versions should usually proceed cleanly without
user intervention, and work as follows:

o    Before package installation, for each database defined in
     /etc/openldap/slapd.conf and any first level included files

o    If no file named
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-imported or
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-import-failed exists
     in the database directory

o    the database will be dumped (using slapcat) to the file
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif in the database
     directory

o    After package installation, for each database defined in
     /etc/openldap/slapd.conf or any first level included files

o    If a file with the name
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif exists, it will be
     imported using slapadd.

o    If the import succeeds, this file will be renamed to
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-imported

o    If the import fails, the file will be renamed to
     rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-import-failed

Thus, under normal circumstances, each database should be migrated
successfully, leaving a file (which could be quite large) named
rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-imported in each database
directory. If you are happy that migration worked successfully and you
wish to reclaim the disk space, make this file an empty file (ie  >
rpm-migrate-to-<OPENLDAP-MAJOR-VERSION>.ldif-imported). If import
fails, you should be left with complete LDIF for each database.

If the export of the database fails, then you may need to use a
compatability package matching your previous OpenLDAP package to
export your data. This will require some work (mainly copying your
usual slapd.conf to the configuration directory for the compatability
version), so even though upgrades should work cleanly, it is
recommended to stop slapd and take an ldif backup manually for each
database before upgrading.

If you would prefer to handle all database upgrading yourself, you can
disable automatic migration by setting AUTOMIGRATE=no in your
/etc/sysconfig/slapd

.1.3. Other versions of OpenLDAP
--------------------------------

The Mageia OpenLDAP packages are usually up-to-date at the time of
version freeze in the distribution. The distribution security update
policy means that updates for OpenLDAP packages will only be provided
in the event of a security vulnerability, and will only address the
specific vulnerability (new versions will not be provided, the
original version will be patched).

As a service to users who prefer to run more up-to-date versions of
OpenLDAP software, the maintainer often provides newer (ie versions
not yet marked as stable) versions in the contrib repository that can
be installed in parallel, and usually attempts to ensure that the
packages rebuild correctly (maintaining their status as they were on
the original distribution) on older distributions. However, these
packages cannot be supported by Mageia.

Compatability packages are kept in contrib for at least one release
after they have been replaced in main by a new version (to ensure that
users for whom automatic migration failed can export their data with a
slapcat compatible with their data. The BerkeleyDB version that the
package used when in main is maintained, even if this means retaining
an internal copy.

OpenLDAP versions (db4 version) in Mageia releases

Release           Main             Newer             Compatability
................. ................ ................. ................ 
Mageia 6          2.4.45 (system   N/A               N/A
                  db5.3.28)
Mageia 5          2.4.40 (system   N/A               N/A
                  db5.3.28)
Mageia 4          2.4.38 (system   N/A               N/A
                  db5.3.21)
Mandriva 2007.1   2.3.34 (system   N/A               2.2.27(system
                  db4.2.52.4+patch)                  db4.2.42.2)

All the files/commands/man pages and OpenLDAP-specific directories (ie
/usr/lib/openldap, /etc/openldap) are suffixed with the major version
of the software, for instance the slapd daemon would be called
slapd2.2 and would use the configuration file
/etc/openldap2.2/slapd.conf and plugins from /usr/lib/openldap2.2).

.1.4. Skip Ahead
----------------

The rest of this chapter may be skipped if the version you require is
available and can be installed with urpmi or the Software Installer.
Continue on to Configuring slapd.

