tracker-store(1) User Commands tracker-store(1)
tracker-store - database indexer and query daemon
tracker-store provides both a powerful database daemon which allows clients to query or update their data using the highly descriptive
tracker-store does not do any file crawling or any mining of data itself, instead other processes do that and serves as a daemon waiting
for such requests from application miners like tracker-miner-fs.
A brief help message including some examples.
Returns the version of this binary.
Sets the logging level, 0=errors, 1=minimal, 2=detailed, 3=debug.
This forces tracker-store to remove databases and to recreate fresh databases ready for data insertion from the miners. For more
information about the miners, see tracker-miner-fs.
This changes the behavior of the database manager and some other parts of tracker-store to be optimized for lower memory systems by
lowering database connection cache sizes and page sizes for example. This may slow down indexing performance.
This starts tracker-store in a mode which disables writing to the database. Only SPARQL read requests can be serviced if this option
This is the directory which tracker uses to load the .ontology files from. If unset it will default to the correct place. This is
used mainly for testing purposes.
This is the directory which tracker uses to load the stop words dictionaries from. If unset it will default to the correct place.
This is used mainly for testing purposes.
This is maximum time allowed for a process to finish before interruption happens. The actual moment of interruption depends also on
the frequency of checks. The value 0 indicates no interruption. This environment variable is used mainly for testing purposes.
TRACKER_STORE_SELECT_CACHE_SIZE / TRACKER_STORE_UPDATE_CACHE_SIZE
Tracker caches database statements which occur frequently to make subsequent repeat queries much faster. The cache size is set to
100 by default for each type (select and update queries). This must be at least 2 as a minimum, any less and a value of 3 is used
instead. The number represents the number of cached statements to keep around. This environment variable is used mainly for testing
Tracker has a fixed set of PRAGMA settings for creating its SQLite connection. With this environment variable pointing to a text
file you can override these settings. The file is a
separated list of SQLite queries to execute on any newly created SQLite con-
nection in tracker-store.
If Tracker is compiled with meegotouch locale management support, setting this variable in the environment will disable retrieving
the locale from GConf, and the standard locale settings will be used instead.
Don't just log to stdout and stderr, but to log files too which are kept in $HOME/.local/share/tracker/. This came into effect in
0.15.3 and 0.16.0. After this version of Tracker, logging to file (usually useful for debugging) can only be done by declaring this
Don't use GSettings, instead use a config file similar to how settings were saved in 0.10.x. That is, a file which is much like an
.ini file. These are saved to $HOME/.config/tracker/
tracker-store is highly bound to the D-Bus freedesktop project. A D-Bus session is needed for all Tracker processes to communicate between
each other. D-Bus is our acting IPC. See dbus-daemon(1) for more information.
tracker-applet(1), tracker-search-tool(1), tracker-search(1), tracker-tag(1), tracker-stats(1), tracker-services(1), tracker-info(1),
September 2009 tracker-store(1)