diff options
| author | Carlos Garnacho <carlosg@gnome.org> | 2022-02-23 11:16:42 +0100 |
|---|---|---|
| committer | Carlos Garnacho <carlosg@gnome.org> | 2022-02-23 11:20:04 +0100 |
| commit | 56cb0b81d2a0d18843d92e1e7ba337463293c866 (patch) | |
| tree | b1f2eadba3ff84f439cf7c4a380a0e1793d92ea1 /docs | |
| parent | edcdecdd7d1246396f3412218e8187bfbf555a29 (diff) | |
| download | tracker-56cb0b81d2a0d18843d92e1e7ba337463293c866.tar.gz | |
website: Mention "tracker3 status" as first stop in debugging
Besides current status, that tells about missing files and whatnot,
seems a good idea to advise that before telling to follow/restart/debug
daemons.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/website/faq.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/website/faq.md b/docs/website/faq.md index 8370cb64d..9decfefae 100644 --- a/docs/website/faq.md +++ b/docs/website/faq.md @@ -117,8 +117,10 @@ to find out what the Tracker daemons are doing. You'll need to use a Terminal program to run these commands. * **Check Tracker daemon status**: You can view live status messages from - Tracker daemons by running: `tracker3 daemon status --follow`. This may - explain what the daemon is currently doing. + Tracker daemons by running: `tracker3 status`. This may explain the current + status of the daemon, and the problems it found. The command: + `tracker3 daemon status --follow` may also be useful to see what the + daemon is doing currently. * **Check the system log**: You can view error logs from Tracker daemons by running this command: |