Displaying 20 results from an estimated 10000 matches similar to: "[FTS Xapian] Beta release"
2019 Jan 13
3
[FTS Xapian] Beta release
Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot:
>
> I tried to combined it, the "autoreconf" errors are solved
>
> Now, when I type "make install", the lib is not pushed into dovecot
> folder, but somewhere in /usr/local/...
>
> How to adjust this to have it arriving in the proper folder ?
>
Depends on your system. It mostly a matter of setting
2019 Jan 14
2
[FTS Xapian] Beta release
In your README.md, perhaps "This project intends to provide a
straightforward and simple *procedure *to configure FTS plugin for Dovecot,
leveraging the efforts by the Xapian.org team." is better??
Also in the part after cloning from git:
./configure --prefix=/usr --with-dovecot=/path/to/dovecot [ This
/path/to/dovecot is not obvious. Is it the dovecot binary or what??]
On Mon, 14 Jan
2019 Jan 14
3
[FTS Xapian] Beta release
Testing a compile on FreeBSD.
gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src'
/bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I.
-I.. -I/opt/dovecot2.3/include/dovecot
-I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD
-MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo
fts-backend-xapian.cpp
libtool:
2019 Jan 14
2
[FTS Xapian] Beta release
Op 14-1-2019 om 13:40 schreef Aki Tuomi:
>
> Just to remind that now that there is a github repo for fts-xapian,
> you could maybe open these issues there instead?
>
Although README.md currently says:
"Please feel free to send your questions, together with the dovecot log
file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML
dovecot at dovecot.org
2019 Jan 13
1
[FTS Xapian] Beta release
Please kindly check https://github.com/grosjo/fts-xapian
On 2019-01-13 20:11, Aki Tuomi wrote:
> If you had looked at what I sent, you'd seen it's quite different from what you sent.
>
> Anyways, put the contents of skeleton.tar.gz and
>
> ./src/plugins/fts-xapian/fts-xapian-plugin.h
> ./src/plugins/fts-xapian/fts-backend-xapian.cpp
>
2019 Jan 14
3
[FTS Xapian] Beta release
Hi,
I installed and tested your version, but the indexer process crashes reproducible with the following command after about 2000 messages were indexed:
doveadm index -u paul at iwascoding.com -q \*
Jan 14 09:26:15 mail dovecot: indexer-worker(paul at iwascoding.com)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Mailbox sent: UID 2038: Opened mail because: fts indexing
Jan 14 09:26:15 mail
2019 Jan 13
2
[FTS Xapian] Beta release
THis is already what I send earlier (see : dovecot-xapian-1.0b2.tar.gz
[1] )
What I would need is the files so one can download (git) it, and type
some command (make ?) to compile it and place it in the right forlder
(/usr/lib/dovecot/ or whatever is configured in the installed dovecot,
which may differ from distribution to distribution)
On 2019-01-13 19:47, Aki Tuomi wrote:
> You need
2019 Jan 13
0
[FTS Xapian] Beta release
I tried to combined it, the "autoreconf" errors are solved
Now, when I type "make install", the lib is not pushed into dovecot
folder, but somewhere in /usr/local/...
How to adjust this to have it arriving in the proper folder ?
On 2019-01-13 21:01, Tuomi, Aki wrote:
> You copied your Makefile.am there. Stephan made you a working version, can you try that?
>
>
2019 Jan 14
0
[FTS Xapian] Beta release
Thank you Stephan.
The version here shall be up and running :
https://github.com/grosjo/fts-xapian
On 2019-01-14 00:07, Stephan Bosch wrote:
> Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot:
>
>> I tried to combined it, the "autoreconf" errors are solved
>>
>> Now, when I type "make install", the lib is not pushed into dovecot folder, but
2019 Jan 14
0
[FTS Xapian] Beta release
THank you Odhiambo. I updated accordingly
On 2019-01-14 08:07, Odhiambo Washington wrote:
> In your README.md, perhaps "This project intends to provide a straightforward and simple PROCEDURE to configure FTS plugin for Dovecot, leveraging the efforts by the Xapian.org team." is better??
> Also in the part after cloning from git:
>
> ./configure --prefix=/usr
2019 Jan 12
2
[FTS Xapian] Status & Questions
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Did you remember to load fts first?
</div>
<div>
<br>
</div>
<div>
mail_plugins =$mail_plugins fts fts_xapian
</div>
<div>
<br>
</div>
<div>
Aki
</div>
2019 Jan 14
0
[FTS Xapian] Beta release
Just to remind that now that there is a github repo for fts-xapian, you
could maybe open these issues there instead?
Aki
On 14.1.2019 14.29, Odhiambo Washington wrote:
> Testing a compile on FreeBSD.
>
> gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src'
> /bin/sh ../libtool? --tag=CXX? ?--mode=compile c++ -DHAVE_CONFIG_H -I.
> -I..?
2019 Jan 14
0
[FTS Xapian] Beta release
Can you send the log part that includes the "init" of the plugins
(something similar as below) ?
WHich version of Xapian are you on ?
Jan 14 09:10:04 gjserver dovecot[31082]:
indexer-worker(admin at grosjo.net)<14725><apZfHexRPFy9QAAA0thIag:UL+TNOxRPFyFOQAA0thIag>:
FTS Xapian: Partial=2, Full=20
DB_PATH=/data/mail/grosjo.net/admin/xapian-indexes
Jan 14 09:10:04 gjserver
2020 Nov 04
2
vsz_limit
You could also add it as setting for the fts_xapian plugin parameters?
Aki
> On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote:
>
>
> For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process)
> I tried to put a
2019 Jan 13
2
[FTS Xapian] Beta release
Ok for having a link on the FTS page.
PLease clarify what files are necessary to package it as a separate
package
On 2019-01-13 19:03, Aki Tuomi wrote:
> Yes, from compiling point of view it is done.
>
> Unfortunately what is not done is all the other work involved, such as fixing all the inevitable bugs it has and maintaining it. We do not want, at this moment, take up maintaining
2020 Nov 06
2
vsz_limit
Duh... src/lib/restrict-process-size.h
Should be in the installed include files as well,
/usr/include/dovecot/restrict-process-size.h
Aki
> On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote:
>
>
> Hello
> I can't find "src/lib/restrict.h" . Is it in dovecot source ?
>
>
> On 2020-11-06 13:20, Aki Tuomi wrote:
> > Seems I had
2019 Jan 13
2
[FTS Xapian] Beta release
The only point here of this fts-xapian is to get rid of solr (because it
is just a nightmare to setup) and squat (because it is considere
obsolete).
I already sent the changed in configure.ac, makefile.am, etc.. in order
to include it in the dovecot, and it compiles properly
The only remaining point is to push it in hte git (yes, everything is
already done)
On 2019-01-13 18:45, Aki Tuomi
2020 Nov 06
1
vsz_limit
Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage.
Aki
> On 06/11/2020 13:26 Joan Moreau <jom at grosjo.net> wrote:
>
>
> yes, will do so.
> It would be nice however to be able to access the actual dovecot config from the plugin side
2019 Apr 21
2
FTS delays
It's because you're misunderstanding how the lookup() function works. It gets ALL the search parameters, including the "mailbox inbox". This is intentional, and not a bug. Two reasons being:
1) The FTS plugin in theory could support indexing/searching any kinds of searches, not just regular word searches. So I didn't want to limit it unnecessarily.
2) Especially with
2019 Apr 21
2
FTS delays
Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue.
> On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote:
>
> For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh