Re: [Tracker] tracker constantly crawling

[Debarshi Ray <rishi is lostca se>]

Hey,

Sorry to butt in. I am just a mere spectator here. :)

On Thu, Nov 30, 2017 at 08:38:08PM +0100, Philip Van Hoof wrote:
> On Thu, 2017-11-30 at 14:21 -0500, Brian J. Murrell wrote:
> > On Thu, 2017-11-30 at 19:46 +0100, Philip Van Hoof wrote:
> > > Ok, I suppose you could contribute a FAM backend for tracker-miner-
> > > fs then. Wouldn't be bad to have support for multiple kinds of
> > > file-monitoring.
> >
> > The original question was that I thought that Tracker already had
> > this (and did it disappear) along with the question of whether
> > Tracker simply crawling NFS shares over and over again (i.e. starting
> > a new crawl as soon as it's done the previous one) is actually the
> > expected behaviour for NFS shares.
>
> The answers to your original question are: no it never had FAM support,
> and no that doesn't sound like expected behavior.

Tracker uses GLib's GFileMonitor API these days, which has various
implementations based on the operating system, file system,
etc.. There are FAM, inotify, kqueue, Windows implementations for
"native" mounts.  Usually, GLib picks the right one and everybody just
goes along with it. That's what Tracker usually does.

However, you can force the issue with the GIO_USE_FILE_MONITOR
environment variable.

Tracker has some awareness of the implementation being used, and it
sets various limits and flags accordingly. See tracker_monitor_init in
tracker.git.

Cheers,
Rishi