Re: [Tracker] Ready for merge

[Philip Van Hoof <spam pvanhoof be>]

On Fri, 2008-08-08 at 03:19 +0200, Laurent Aguerreche wrote:
> Le vendredi 08 aoÃt 2008 Ã 02:11 +0200, Philip Van Hoof a Ãcrit :

> Indeed, I was a little bit too enthusiastic because Firefox is also
> getting frozen from time to time but I can switch from an application to
> another so it is still better.

Hmmk. Let's try to find out why trackerd still causes these sporadic
freezes then.

I think it's related to the rapid initial crawling of hundreds of
directories and files. But it might also be related to other things.

> I noticed that tracker-indexer has not an idle priority for I/O. The
> program written in configure.ac does not correctly check whether I can
> set I/O priorities on my system. IMHO it misuses the AC_LANG_PROGRAM
> macro, and I do not understand why it uses exit() instead of return!? I
> propose a patch (but, to be honest, I only fixed the use of M4 macros).
> This fix works on my Fedora 9 x64. I can commit in trunk and
> indexer-split branches if this patch is assumed to be correct.


Make a patch and send it to this mailing list (for both TRUNK and
indexer-split). We will (martyn probably will) review the indexer-split
one and if okay we'll approve (so that you can commit in indexer-split).

Once in indexer-split it'll get merged to TRUNK automatically soon.

> And a question, why do I see this message often:
>
> Tracker-Message: Items could not be processed by the indexer, Did not
> receive a reply. Possible causes include: the remote application did not
> send a reply, the message bus security policy blocked the reply, the
> reply timeout expired, or the network connection was broken.

That happens because trackerd causes other processes, like tracker-
indexer, to hang. Making tracker-indexer reply after a too long delay
for trackerd. Trackerd copes with this situation by retrying it.

> All around it, I get this message:
> Tracker-Message: Still waiting for response from indexer, not sending
> more files yet
> It appears 12 times, then I get the previous message! It's like a loop.

Those messages where my own initial reason why I made the patch that I
attached. Does it happen with or without the patch applied, or both?

 
-- 
Philip Van Hoof, freelance software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://pvanhoof.be/blog
http://codeminded.be