tracker-miner-fs(1) [centos man page]
tracker-miner-fs(1) User Commands tracker-miner-fs(1) NAME
tracker-miner-fs - Used to crawl the file system to mine data. SYNOPSIS
tracker-miner-fs [OPTION...] DESCRIPTION
tracker-miner-fs is not supposed to be run by the user since it is started by its .desktop file when the user logs in. It can also be started manually of course for debugging purposes. You can not run more than one instance of this at the same time. tracker-miner-fs mines information about applications and files only. OPTIONS
-?, --help Show summary of options. -V, --version Returns the version of this binary. -v, --verbosity={0|1|2|3} Sets the logging level, 0=errors, 1=minimal, 2=detailed, 3=debug. -s, --initial-sleep=SECONDS Sets the initial sleep time before crawling the file system is started. If the --no-daemon option is used, this option is ignored. -n, --no-daemon Tells the miner to exit once all indexing has finished and the database is up to date. This is not the default mode of operation for the miner, usually it stays around acting like a daemon to monitor file updates which may occur over time. This option renders the --initial-sleep option moot. -e, --eligible=FILE Checks if FILE is eligible for being mined based on the current configuration rules. In addition to this, it will check if FILE would be monitored for changes. This works with non-existing FILE arguments as well as existing FILE arguments. -d, --disable-miner=MINER Tells the daemon to disable the in-house miners it supports. Depending on build options, this can be 'Files', 'Applications' and 'Userguides'. This option can be provided more than once to diasable multiple miners. Disable in this case means the miner is not started, though all miners still register themselves on D-Bus and appear there, no actual action is performed otherwise (such as crawling, setting up monitors, or checking mtimes against the file system). ENVIRONMENT
TRACKER_USE_LOG_FILES 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 environment variable. TRACKER_USE_CONFIG_FILES 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/ SEE ALSO
tracker-store(1), tracker-info(1). GNU
September 2009 tracker-miner-fs(1)
Check Out this Related Man Page
tracker-store(1) User Commands tracker-store(1) NAME
tracker-store - database indexer and query daemon SYNOPSIS
tracker-store [OPTION...] DESCRIPTION
tracker-store provides both a powerful database daemon which allows clients to query or update their data using the highly descriptive SPARQL language. 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. OPTIONS
-?, --help A brief help message including some examples. -V, --version Returns the version of this binary. -v, --verbosity={0|1|2|3} Sets the logging level, 0=errors, 1=minimal, 2=detailed, 3=debug. -r, --force-reindex 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. -m, --low-memory 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. -n, --readonly-mode This starts tracker-store in a mode which disables writing to the database. Only SPARQL read requests can be serviced if this option is used. ENVIRONMENT
TRACKER_DB_ONTOLOGIES_DIR 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. TRACKER_LANGUAGE_STOP_WORDS_DIR 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. TRACKER_STORE_MAX_TASK_TIME 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 purposes. TRACKER_PRAGMAS_FILE 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. TRACKER_DISABLE_MEEGOTOUCH_LOCALE 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. TRACKER_USE_LOG_FILES 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 environment variable. TRACKER_USE_CONFIG_FILES 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/ NOTES
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. SEE ALSO
tracker-applet(1), tracker-search-tool(1), tracker-search(1), tracker-tag(1), tracker-stats(1), tracker-services(1), tracker-info(1), tracker-control(1), http://www.w3.org/TR/rdf-sparql-query/ dbus-daemon(1), http://www.freedesktop.org/wiki/Software/dbus GNU
September 2009 tracker-store(1)