Index: README =================================================================== --- README (revision 587) +++ README (working copy) @@ -223,19 +229,25 @@ if you dont want your entire home direct You can disable indexing by passing --no-indexing You can enable a low memory usage mode (recommended for machines with less -than 256MB of RAM) by passing --enable-low-memory +than 256MB of RAM) by passing --low-memory You can artificially throttle indexing by passing --throttle=value where value -is in the range 0-20 (with 0, the default, being fastest and 20 being slowest). +is in the range 0-20 (with 0 being fastest and 20 being slowest). Default is 0. You should only change this value if you want to prevent noisy fans or hot laptops arising from cpu intensive indexing. Tracker should have a negligible impact on the system (as it is scheduled) so you can safely work with it on full throttle without experiencing slow downs. You can specify directory roots to be excluded from being watched or indexed -by passing -e directory for each directory root +by passing -e directory for each directory root. + +You can specify logging verbosity by passing --verbosity. Valid values are +from 0 to 3, ranging from least to most verbose respectively. -All the above options (and more) can be set by editing ~/.Tracker/tracker.cfg +Yet another option is --language which allows for specifying the language to +use for stemmer and stop-words list. + +All the above options (and more) can be set by editing ~/.config/tracker.cfg which is created with specific defaults when non-existent (EG when trackerd is ran for the first time). Ensure that you restart trackerd for the changes to take effect. tracker.cfg also provides options that allows tracker @@ -247,6 +259,9 @@ EG: WatchDirectoryRoots=directory1;directory2;directory3 +An additional option, introduced during the 0.6 development cycle, is the +--reindex option which indexes user data from scratch, removing the need to +remove Tracker database manually. On the first run, Tracker will automatically create a new database and start populating it with metadata by browsing through the user's home directory (or