Issue #369 has been updated by Clément OUDOT.
Yes, if you modified the schema files provided by OpenLDAP, they are not kept with the upgrade. But if you added custom schema in the schema directory, then no problem with the upgrade. ---------------------------------------- Feature #369: Upgrading OpenLDAP and debugging procedures http://tools.lsc-project.org/issues/369 Author: Nick Milas Status: Assigned Priority: Normal Assigned to: Category: OpenLDAP RPM Target version: Hi, Just a question: Can we simply upgrade your really fine LTB OpenLDAP releases e.g. from v2.4.26 to .27 by running rpm -Uvh ? Will upgrade respect (keep safe): 1. Current Configuration (cn=config or slapd.conf based as specified in /usr/local/openldap/etc/openldap/)? 2. Actual data and custom DB_CONFIG file (as maintained by BDB in /usr/local/openldap/var/openldap-data/)? 3. Custom schema directory in default directory (/usr/local/openldap/etc/openldap/)? Default schema directory in our installation includes custom schemas. 4. Customized /etc/default/slapd? 5. Customized ldap.conf (in /usr/local/openldap/etc/openldap/)? 6. Any other custom settings (which?)? ...or we should keep backups and restore after upgrade? Yes, I know backups are always welcome, but I am wondering about the normal/expected upgrade procedure/behavior. Also, if we want to use the debugging package in order to do back trace with debugging symbols, is there any suggested practice/methodology? Please, advise! Thanks both for your packages and for your assistance, Nick -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________ ltb-dev mailing list [email protected] http://lists.ltb-project.org/listinfo/ltb-dev
