Getting Started


Tracker is split up into several main components. They are:


The data store and daemon to interface to Tracker's databases


The file system crawler to mine data from local files


The meta-data extraction application used on each file


The application for writing meta-data back to files

To illustrate the relationships between libraries in the tracker stack, see how tracker-store and tracker-miner-fs are designed architecturally.

User Interfaces

There are very few user interfaces. Tracker tries to be an integrated tool not to the desktop. There are some UIs that can help test Tracker though:


A GTK+ UI to edit the Tracker configuration for what's indexed and where


A GTK+ UI search application covering tags, music, emails, images, documents and much more...

Some plugins allow you to use Tracker in GNOME applications, for example: Totem and Nautilus.

Command Line Tools

There are also a range of command line utilities to use with Tracker:


Manage Tracker processes and data


Get all information about one or more files/resources


Search for terms in all data


Show statistics for all Nepomuk defined ontology classes


Query or update using SPARQL


Add, remove or list tags


Monitor and control status (no longer exists since 0.9.37, use tracker-control instead)


Tracker uses GSettings for configuration (since 0.12), you can tell Tracker to use the old method of configuration files with environment variables. In the case of configuration files, the configuration is kept in $XDG_CONFIG_HOME/tracker (usually $HOME/.config/tracker).

With GSettings, you can get a quick glimpse of the settings using:

$ gsettings list-recursively | grep -i org.freedesktop.Tracker | sort | uniq

You can also use tools like dconf-editor to use a graphical interface to edit the configuration.

For more information, see the Tracker configuration page.

Data & Logging

The databases are kept in $HOME/.cache/tracker. The user's data backup is kept in $HOME/.local/share/tracker/data.

If Tracker is configured to have the logging verbosity (set in GSettings or each .cfg file for each main component) set to a value higher than 0, then logs are generated and stored in $HOME/.local/share/tracker. See also the tracker-control --set-log-verbosity and it's equivalent command line to get the log verbosity for an easy way to change this.

Projects/Tracker/Documentation/GettingStarted (last edited 2014-02-28 11:26:06 by MartynRussell)