conversations: 0
stop squatter
rm -r everything under search/*
change to conversations_db: twoskip
and then set conversations to 1 and restart squatter
?
Quoting Lists Nethead :
This error started after update to 3.0.12 yesterday.
No idea where to start - hints anyone?
Thanks,
Per
Cyrus Home
This error started after update to 3.0.12 yesterday.
No idea where to start - hints anyone?
Thanks,
Per
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
Quoting Albert Shih :
Le 10/10/2018 à 07:41:52+0200, Lists Nethead a écrit
Quoting Albert Shih :
> Le 09/10/2018 à 21:26:28+0200, Lists Nethead a écrit
>>
>> Quoting Lists Nethead :
>>
>> > > Hi,
>> > >
>> > > A user clicks on a mail
Quoting Albert Shih :
Le 09/10/2018 à 21:26:28+0200, Lists Nethead a écrit
Quoting Lists Nethead :
> > Hi,
> >
> > A user clicks on a mail in Horde IMP and next the inbox appears
> > completely empty. This message files all still there of course, but
> > the pr
Quoting Lists Nethead :
Hi,
A user clicks on a mail in Horde IMP and next the inbox appears
completely empty. This message files all still there of course, but
the problem is that I cannot run any cyrus command on that mailbox,
reconstruct, chk_cyrus or anything.
Is there a lock
Hi,
A user clicks on a mail in Horde IMP and next the inbox appears
completely empty. This message files all still there of course, but
the problem is that I cannot run any cyrus command on that mailbox,
reconstruct, chk_cyrus or anything.
Is there a lock possibly sitting somewhere
Hi,
A user clicks on a mail in Horde IMP and next the inbox appears
completely empty. This message files all still there of course, but
the problem is that I cannot run any cyrus command on that mailbox,
reconstruct, chk_cyrus or anything.
Is there a lock possibly sitting somewhere
Quoting Hajimu UMEMOTO :
Hi,
On Wed, 14 Feb 2018 11:25:12 -0600
Nic Bernstein said:
I do understand that managing a project like this is quite a task
and v.3 is still young. Apart from the log issue and xapian I also
stumbled over other undocumented
Quoting Nic Bernstein :
[...]
Per,
I've created an issue #2248 for this on GitHub, and have just
created PR #2249 which addresses it. Thanks for your feedback.
As for the FreeBSD path changing issues, that's up to the package
creator. Please let them know.
Cheers,
eneral, the mailing is a grand place to start, and IRC is also
your friend (#cyrus on freenode).
Cheers,
-nic
On 02/14/2018 04:58 AM, Lists Nethead wrote:
Quoting Sebastian Hagedorn <haged...@uni-koeln.de>:
--On 14. Februar 2018 um 11:13:15 +0100 Lists Nethead
<li...@nethead.se> wrot
Quoting Sebastian Hagedorn <haged...@uni-koeln.de>:
--On 14. Februar 2018 um 11:13:15 +0100 Lists Nethead
<li...@nethead.se> wrote:
I am testing Xapian in a 3.0.5 setup on FreeBSD using most default
setting. If I start imapd with "squatter cmd="squatter -R&quo
Hi,
I am testing Xapian in a 3.0.5 setup on FreeBSD using most default
setting. If I start imapd with "squatter cmd="squatter -R", more and
more "squatter" processes are created and eventually grabs all
resources.
The mail store is only 136G but it seems like the system wants to
index
12 matches
Mail list logo