Hi... again.
I'm sorry for all the replies to my own posts. However, I checked the
man page for ctl_cyrusdb(8) and saw the "-x" flag.
-x Used with -r to recover the database only. (Prevents
database cleanup).
With this in mind, I went back to the source code and discovered that if
Greetings!
More info on the subject:
In cyrus.conf:
START {
# do not delete this entry!
recover cmd="ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
idled cmd="idled"
}
Observe the comment "do not delete this entry". Now, looking at the code
in ctl_cyru
Eddy Beliveau wrote:
Strange!,
My delprune event for cyrus 2.1.16 is:
delprune cmd="ctl_deliver -E 3" at=0400
also, 'man cyr_expire' doesn't exist on my system
Yeah, that's the way it's done in 2.1.x. We're running 2.2.x. Excerpt
from docs:
"Upgrading from 2.2.0 or earlier:
ctl_deliver -E h
Bill Earle wrote:
On Thu, 7 Oct 2004, Jules Agee wrote:
> I've had this happen a few times, reconstructing the deliver db on
> startup.
>
Look at the man page for "cyr_expire" and "cyrus.conf".
delprune cmd="cyr_expire -E 3" at=0400
This is our EVENTS section:
EVENTS {
checkpointcmd="
Greetings!
We've been running the Cyrus IMAP server for couple of months now. Apart
from the server experiencing high load (we'll throw money at it and see
what happens) from time to time, it's mostly been smooth sailing.
However, one thing is a bit worrying. Startup of the Cyrus software
takes
