tags 377812 = confirmed thanks > In any case, I assume the Debian upgrade script does the right thing as > far as doing backups, i.e., it iterates over the entire slapd.conf file, > looking for every occurrence of the "database" keyword, and then backs up > each of those databases individually in their own LDIF file, and skips any > unsupported database backends for backups.
This appears to not be the case. I don't think that any consideration was given, when this code was written, to the possibility that a failure to slapcat a database would be anything but a fatal error that should cause the upgrade to abort. This should be corrected in the Debian package. back-sql clearly needs to be excluded, since we have no way to slapcat it; back-ldap should as well, I think, because the backend storage format is obviously stable. ;) What other backends should be excluded? (I think this should be a list of exclusions rather than inclusions, because I would rather assume by default that we *should* back up a directory unless we have a concrete reason to believe this isn't needed.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
