After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 613256 - Disable crawler by default
Disable crawler by default
Status: RESOLVED FIXED
Product: tracker
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: tracker-indexer
Jamie McCracken
Depends on:
Blocks: 613258 659025
 
 
Reported: 2010-03-18 17:00 UTC by Bastien Nocera
Modified: 2011-09-14 09:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2010-03-18 17:00:12 UTC
Or at least make it opt-in, otherwise applications cannot drive the indexing, and will rely on the tracker indexer getting to their data "at some point", and with no easy way to tell the indexer to index specific locations, or ignore some others.
Comment 1 Carlos Garnacho 2010-04-26 10:24:06 UTC
Would a dbus method + higher priority queue in tracker-miner-fs work for you? IMHO, having indexing fully driven by applications is going to be prone to having outdated info in the store, given the amount of applications, and the lack of guarantees on when they'll be started.

So, at much we could be adding some configuration option to have the crawler kick in past given interval (say, once a week), but we're really hoping on fanotify to make crawling something from the past.
Comment 2 Martyn Russell 2010-05-17 13:30:02 UTC
Moving "Indexer" component bugs to "General" since "Indexer" refers to the old 0.6 architecture
Comment 3 Bastien Nocera 2010-08-12 10:41:22 UTC
(In reply to comment #1)
> Would a dbus method + higher priority queue in tracker-miner-fs work for you?

Not really.

> IMHO, having indexing fully driven by applications is going to be prone to
> having outdated info in the store, given the amount of applications, and the
> lack of guarantees on when they'll be started.

Well, that problem already exists for applications. See the crawling/indexing done by banshee, F-Spot or Rhythmbox.

> So, at much we could be adding some configuration option to have the crawler
> kick in past given interval (say, once a week),

That really wouldn't help. If I start my app, I expect the data to be indexed _now_ (or before I even start the app) if there's any new data.

> but we're really hoping on
> fanotify to make crawling something from the past.

fanotify is now in the kernel. Is there a separate bug about using it?
Comment 4 Jamie McCracken 2010-08-12 12:36:43 UTC
> fanotify is now in the kernel. Is there a separate bug about using it?

we would need more details about fanotify. In particular we would need the file name of any changed file but if fanotify only returns an fd then we may have problems here (http://lwn.net/Articles/339399/)
Comment 5 Jamie McCracken 2010-08-12 16:38:43 UTC
that said its possible on linux to get filename from fd but in a hacky way

it does mean going into /proc/(tracker-miner pid)/fd and using readlink on the fd number

If anyone knows a cleaner way let us know!
Comment 6 Martyn Russell 2010-12-08 10:01:49 UTC
This bug has been fixed for a while. Tracker has an option to disable the miner-fs but it doesn't happen by default yet.

See $HOME/.config/tracker/tracker-miner-fs.cfg and the key CrawlingInterval. If set to -1 crawling is disabled entirely.

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.