Commit 23509b05 authored by Sam Thursfield's avatar Sam Thursfield
Browse files

README: Remove more obsolete info

Most of the tools referenced in "Running Tracker" don't exist any more.

We shouldn't need to document how to set inotify limits as distros
should be setting inotify limits high enough for Tracker to work out of
the box.

The man pages referred in the "Further help" section are nice, but
ideally they'd be linked from the main documentation at (see
parent ea4263b5
......@@ -53,54 +53,3 @@ with files not being installed correctly. (You may need to copy
and amend the dbus service file to the correct directory and/or
might need to update ld_conf if you install into non-standard
## Running Tracker
### Usage
Tracker normally starts itself when users log in. You can indexing by running:
You can configure how this works using:
You can monitor data miners using:
You can do simple searching using an applet:
You can do more extensive searching using:
### Setting Inotify Watch Limit
When watching large numbers of folders, its possible to exceed
the default number of inotify watches. In order to get real time
updates when this value is exceeded it is necessary to increase
the number of allowed watches. This can be done as follows:
1. Add this line to /etc/sysctl.conf:
"fs.inotify.max_user_watches = (number of folders to be
watched; default used to be 8192 and now is 524288)"
2. Reboot the system OR (on a Debian-like system) run
"sudo /etc/init.d/procps restart"
## Further Help
### Man pages
Every config file and every binary has a man page. If you start with
tracker-store, you should be able to find out about most other
commands on the SEE ALSO section.
### Utilities
There are a range of tracker utilities that help you query for data.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment