Re: Initial use of Xapian

On Mon, Feb 19, 2018, at 11:38 AM, ellie timoney wrote: > Hmm. I suspect the -R and -n options are mutually exclusive. -n is a > one-shot run of the named channel (as you see); -R is the rolling mode > (with no way to specify the channel). And it looks like, as you've > discovered, the -n

Re: Initial use of Xapian

On Fri, Feb 16, 2018, at 4:02 AM, Lists Nethead wrote: > Some more observations, > > - When placed in START section, "squatter cmd="squatter -R -n > squatter", the process does the log and then just vanishes and does > nothing more while the "squatter" log just grows. Hmm. I suspect the -R

Re: Initial use of Xapian

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

Re: Initial use of Xapian

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 changes related to FreeBSD only I

Re: Initial use of Xapian

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,

Re: Initial use of Xapian

(re-sending this for the list, because I sent from the wrong address and it got eaten, doh!) On Thu, Feb 15, 2018, at 1:32 PM, ellie timoney wrote: > The change in the install directories for binaries occurred at the start > of the 3.0 series, and is documented in the 3.0.0 release notes: > >

Re: Initial use of Xapian

On 02/14/2018 11:04 AM, Per olof Ljungmark wrote: Quoting Nic Bernstein : On 02/14/2018 10:35 AM, Lists Nethead wrote: Quoting Nic Bernstein : The advice to move it to START is actually based on a recently discovered bug, referred to in that issue report

Re: Initial use of Xapian

On 02/14/2018 10:35 AM, Lists Nethead wrote: Quoting Nic Bernstein : The advice to move it to START is actually based on a recently discovered bug, referred to in that issue report (#2234). It /should/ be in DAEMON, but for that bug, which has been fixed. The fix will be in

Re: Initial use of Xapian

Quoting Nic Bernstein : The advice to move it to START is actually based on a recently discovered bug, referred to in that issue report (#2234). It /should/ be in DAEMON, but for that bug, which has been fixed. The fix will be in the next release. In general, the

Re: Initial use of Xapian

The advice to move it to START is actually based on a recently discovered bug, referred to in that issue report (#2234).  It /should/ be in DAEMON, but for that bug, which has been fixed.  The fix will be in the next release. In general, the mailing is a grand place to start, and IRC is also

Re: Initial use of Xapian

Quoting Sebastian Hagedorn : --On 14. Februar 2018 um 11:13:15 +0100 Lists Nethead 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", more and more "squatter"

Re: Initial use of Xapian

--On 14. Februar 2018 um 11:13:15 +0100 Lists Nethead 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", more and more "squatter" processes are created and eventually grabs all resources.

Initial use of Xapian

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