|
a/website/faqsandhowtos/WhyIsMyFileNotIndexed.txt |
|
b/website/faqsandhowtos/WhyIsMyFileNotIndexed.txt |
|
... |
|
... |
56 |
|
56 |
|
57 |
In case of indexer misbehaviour (e.g. using too much memory, you should run
|
57 |
In case of indexer misbehaviour (e.g. using too much memory, you should run
|
58 |
_tail -f_ on the log to see what is going on.
|
58 |
_tail -f_ on the log to see what is going on.
|
59 |
|
59 |
|
60 |
If this is not enough, please
|
60 |
If this is not enough, please
|
61 |
link:http://bitbucket.org/medoc/recoll/issues/new[open a tracker issue] and
|
61 |
link:https://opensourceprojects.eu/p/recoll1/tickets/new/[open a tracker
|
62 |
attach or link to the log data, or just email me (jfd at recoll.org).
|
62 |
issue] and attach or link to the log data, or just email me (jfd at
|
|
|
63 |
recoll.org).
|
63 |
|
64 |
|
64 |
*recollindex* and *recollindex -i* usually have the same criteria to
|
65 |
*recollindex* and *recollindex -i* usually have the same criteria to
|
65 |
include a file or not (but see the _Path gotcha_ note below). It may
|
66 |
include a file or not (but see the _Path gotcha_ note below). It may
|
66 |
happen that they behave differently, so it may sometimes be useful to run a
|
67 |
happen that they behave differently, so it may sometimes be useful to run a
|
67 |
full *recollindex* even for a specific file, but this will produce a
|
68 |
full *recollindex* even for a specific file, but this will produce a
|