Hello, I recently built Cyrus 2.0.12, got it compiled (Rh6.2, I think I have evaded the db3 problems that seem to run rampant), followed the HOWTO on the initial steps, then started it. ctl_mboxlist has been running (as -r, specified in cyrus.conf) for 45 minutes, and still going, using 99.6+% of the CPU. I cannot connect, of course, as it has not forked off the actual daemons; master started ctl_mboxlist and that's all has happened. I am unsure where to begin looking. I saw no refs in the list archives to a problem like this. Is there a way to mark the initial database(s) as clean, so it won't try to recover them when I start? Cyrus 2.0.12 (from source) SASL 1.5.24 Sleepycat DB 3.2.9 (from source) Red Hat 6.2 on a P2/400 w/ 256MB RAM, kernel 2.2.17 Cheers and TIA, -- J. Gregg Thomason Penguin Wrangler, Barefoot Software
