Hi everyone,
Another follow-up to my monologue thread - I've had a few helpful
replies off-list though, and comments (on or off list) are very much
appreciated.
I've started building cyrus-imapd-2.2.13 - the Cyrus homepage still
lists 2.2.12 as the 'current' version, but is apparently outdat
On Tue, 29 Aug 2006, Paul Boven wrote:
Progress made since:
I've tried to build a Cyrus without any Berkeley by specifying
'--without-bdb' - for that, I had to comment out a fixed '#include ' in
lib/auth_pts.h. But that only resulted in this error message when starting
up: "Fatal error: cyru
Hi everyone,
Paul Boven wrote:
If I build cyrus against the old version (4.1.25), it runs great. If I
build it against 4.4.20, it doesn't want to start. Even though I've
changed tlscache_db and duplicate_db to 'skiplist' in the imapd.conf and
removed those db-files from the system, so it shoul
On Mon, 28 Aug 2006, Paul Boven wrote:
Hi everyone,
A bit over a month ago I tried to upgrade the Berkeley DB on a Cyrus-2.2.12
mailserver. That didn't work out because right at startup, 'ctl_cyrusdb -r'
would fail with 'critical dabase situation'.
After a bit of debugging, I've gotten thin
Hi everyone,
A bit over a month ago I tried to upgrade the Berkeley DB on a
Cyrus-2.2.12 mailserver. That didn't work out because right at startup,
'ctl_cyrusdb -r' would fail with 'critical dabase situation'.
After a bit of debugging, I've gotten things down to this:
If I build cyrus agains
