Hi Torsten, Torsten Landschoff torsten-at-debian.org |bugs-debian| wrote: > Do you have a suggestion how to improve the wording so this isn't > interpreted wrongly?
Patch attached. I hope it makes things clearer. >>So I want to change the directory location to which the backups are made >>but I did not find any other way than calling dpkg-reconfigure, which is > > ... which you don't want to do since it will create a new LDAP database > from scratch. Maybe that's something to change as well. Uh-oh. Thank god I hesitated and looked after another way to reset the values. Unfortunately my search with Google and different mailing lists were fruitless. >>So it would be really nice when those options could be set via a shell >>snippet in /etc/default, or alternatively the slapd/dump_database_destdir > > Hmm, did not want to do that since I don't want to repeat configuration > settings all around. Maybe I'll add the option to overwrite it from > there which will stop debconf from ever asking it. Let's see... I had a look at your postinst script and though it is wonderfully structured it will be lot of work to migrate settings from debconf to a shell script. Though a worthy goal since editing a shell script with a text editor gives you more freedom then editing variables by using debconf (from a user's point of view). And more freedom is always needed when dealing with a package as complex as OpenLDAP :) >>setting is asked each time when an upgrade is performed (which would make >>sense anyway since free space on the partitions is probably subject to >>change). Calling "db_fset slapd/dump_database_destdir seen false || true" > > It will also annoy users so I don't want to got along that route. The > question is mostly there anyway so that the backup is on the same > partition as the mv command will then be very quick. > > Quick work around for you: > echo FSET slapd/dump_database_destdir seen false|debconf-communicate You are probably right - setting the dump_database_destdir entry once and for all should be sufficient for most installations. Having this value in a shell scriptlet would be nice for easy manipulation but implementing this takes surely some time. In the meantime thanks for sharing the above command with me, it did the trick. Truly a command to remember! Thank you for your fast response, Thomas Prokosch
--- slapd.templates 2005-04-01 18:59:49.000000000 +0200 +++ /tmp/slapd.templates 2005-04-13 17:58:55.928198366 +0200 @@ -10,18 +10,24 @@ Choices: always, when needed, never Default: when needed Description: Dump databases to file on upgrade - Before upgrading to a new version of the OpenLDAP server the data of - your LDAP directories can be dumped to plain text files (LDIF format) - which is a standardized description of that data (LDIF stands for - LDAP Data Interchange Format). + Upgrading to new versions of OpenLDAP sometimes require rebuilding the + database. This can be done automatically when the database is dumped + into a standardized plain text file first. Such files are called LDIF + files. With this question you can specify whether an automatic upgrade + should happen. Only answer "always" if a dump should also happen even + though the database format did not change. Template: slapd/dump_database_destdir Type: string Default: /var/backups/slapd-VERSION Description: Directory to dump databases You can specify into which directory the LDAP databases are to be - exported. The string VERSION is replaced with the server version you - are upgrading from. + exported. Within this directory several LDIF files are created which + correspond to the search bases located on the server. Make sure you have + enough free space on the partition the directory is located. + The first occurrence of the string "VERSION" is replaced with the server + version you are upgrading from. The default is + /var/backups/slapd-VERSION Template: slapd/move_old_database Type: boolean
