[Kolab-devel] [issue1031] kolabconf should not require running ldap to update slapd.conf

[Bernhard Herzog]

New submission from Bernhard Herzog <bh at intevation.de>:

When doing an upgrade, especially when the openldap version changes, it can
happen that the new openldap doesn't work with the old slapd.conf file. 
Unfortunately, even if the new kolabd is accompanied by an updated
slapd.conf.template, the slapd.conf file cannot be generated from
slapd.conf.template because kolabconf requires a running openldap.

It would be helpful if kolabconf could be used to generate slapd.conf anyway if
it only needs values taken from kolab.conf so that openldap is not actually
required.  For the slapd.conf.template provided by kolab this is the case.

This would be helpful for the upgrade to OpenPKG 2.5 since that has a new
openldap which doesn't work with the old slapd.conf.

----------
assignedto: steffen
messages: 6067
nosy: bh, steffen
priority: wish
status: unread
title: kolabconf should not require running ldap to update slapd.conf
topic: kolab-2.1, server
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1031>
________________________________________________