Your message dated Sat, 15 Jul 2006 22:32:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#304478: Possibility to change slapd/dump_database_destdir
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Severity: normal
Yesterday I upgraded from slapd 2.1 to version 2.2. I was asked where I
wanted to store the database dump. However I misinterpreted the question,
the "VERSION" hint made me think that I was asked for a filename template
within an already existing directory. Later I realized that I was asked for
a directory name only, without the filename part.
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
kind of cumbersome since I do not want to set the other options again (such
as passwords or organization name etc).
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
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"
after the database upgrade has been finished would probably be enough to
solve this problem.
Thanks for your effort,
Thomas
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
This bug is fixed in another way, the templates are improved and the
code is a little big improved.
Thanks for the work.
Regards,
Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEuVDo2n1ROIkXqbARApj6AJ0TK6cUmcU04DIlrdH/AWgL/684nQCgkKMu
sLofM8CrrdlzepnylnN2I+o=
=GGk9
-----END PGP SIGNATURE-----
--- End Message ---
