Problem moving cyrus installation from 32 -> 64 bit system

[Michael Loftis]

--On Saturday, December 11, 2004 03:30 +0100 Palle Girgensohn 
<girgen at pingpong.net> wrote:

> Hi!
>
> I'm trying to move an entire cyrus installation from FreeBSD 4.10 on IA32
> (aka x386) to a new Dell 2850 running FreeBSD 5.3 (amd64, or really
> EM64T).
>
> I use DB3, 3.3.11, on both machines.
> Cyrus imapd 2.2.8 on the old one, 2.2.10 on the new one.
>
> I've dumped/restored /var/imap & /var/spool/imap to the new system. The
> db3 files, deliver.db and tls_sessions.db, I had to db_dump @ old system
> && db_load back on the new system; it seems db3 uses a native format that
> differs between 32 & 64 bit, ctl_cyrusdb -r crashed signal 11 otherwise.

I don't recall offhand if cyrus automatically re-creates them but both 
tls_sessions.db and deliver.db are (fairly) safe to zero out, 
tlse_sessions.db is definitely, and deliver.db is mostly safe.  deliver is 
use to de-duplicate messages.  Hence why it is purged of entries older than 
N days (I use 3, others may use more or less)


---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html