At 11:36 AM 6/17/2003 -0400, Rob Siemborski wrote:
On Tue, 17 Jun 2003, Jim Howell wrote:
The first time through I let it run for 15 minutes, the done
message came
in 81 seconds. Should I of let it keep going? What can I do to
prevent
this from happening again? Thanks.
Most
On Tue, 17 Jun 2003, Jim Howell wrote:
However the ctl_cyrusdb -r process didn't end, it appeared to start
looping. I rebuilt the mailboxes.db from a text backup (ctl_mboxlist
-d output). But to no avail. I still received the recovered
message. I finally just killed the ctl_cyrusdb -r
On Tue, 17 Jun 2003 10:54:06 -0400 (EDT)
Rob Siemborski [EMAIL PROTECTED] wrote:
Most likely it was processing your duplicate delivery database, which
can be quite large and take some time to process (you can generally tell
what is going on by truss/strace on the process).
Options you have
On Tue, 17 Jun 2003, Jim Howell wrote:
The first time through I let it run for 15 minutes, the done message came
in 81 seconds. Should I of let it keep going? What can I do to prevent
this from happening again? Thanks.
Most likely it was processing your duplicate delivery database,
Hi,
Comments below.
Jim
At 10:54 AM 6/17/2003 -0400, Rob Siemborski wrote:
On Tue, 17 Jun 2003, Jim Howell wrote:
However the ctl_cyrusdb -r process didn't end, it appeared to start
looping. I rebuilt the mailboxes.db from a text backup (ctl_mboxlist
-d output). But to no avail. I
On Tue, 17 Jun 2003, Jure Pecar wrote:
I'm seeing the same on my 2.2.0a here ... deliverdb is now at 826mb, i
have checkpoint event set with period=10 and i find one or two ctl_deliver
processes running, eating all the cputime available. strace shows it's
chewing the db files as it should ...
On Tue, 17 Jun 2003, Jure Pecar wrote:
On Tue, 17 Jun 2003 10:54:06 -0400 (EDT)
Rob Siemborski [EMAIL PROTECTED] wrote:
Most likely it was processing your duplicate delivery database, which
can be quite large and take some time to process (you can generally tell
what is going on by
