Upgrading cyrus

Dan White dwhite at olp.net
Fri Sep 10 20:52:59 UTC 2010


On 10/09/10 15:43 -0500, Dan White wrote:
>Which goes on to use the slapcat utility to convert the native format (e.g.
>Berkeley) into a portable LDIF, then reloads under the upgraded version.
>
>That should work for cyrus, and its cvt_cyrusdb utility, by converting to a
>temporary flat file for each database and then converting back (with lots
>of testing of course). I would not bother converting duplicate_db,
>tls_cache, and pts_cache.

Responding to myself here.

I would prompt the user to ask of they wish to convert these databases, but
encourage them not to, since those are probably going to be the most
problematic. If the user says no, then empty databases (for delivery, tls,
and pts) are generated.

>Note that you don't have any preknowledge about the format of any database
>without referencing /etc/imapd.conf. The database format type may have been
>customized.

Referencing the /usr/lib/cyrus/cyrus-db* files makes more sense than
reading /etc/imapd.conf (the admin may have even customized it's location).

-- 
Dan White



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list