1tracker-daemon(1)                User Commands               tracker-daemon(1)
2
3
4

NAME

6       tracker-daemon  - Start, stop, restart and list daemons responsible for
7       indexing content
8
9

SYNOPSIS

11       tracker daemon [options...]
12       tracker daemon -s | -t [daemons] | -k [daemons] | -l
13       tracker daemon -f | -w [ontology]
14       tracker daemon --miner <miner> --pause[-for-process] <reason>
15       tracker daemon --miner <miner> --resume <cookie>
16
17
18

DESCRIPTION

20       Tracker has many components to it including a "store" for handling data
21       set  updates  and "miners" for handling data mining in their respective
22       areas.
23
24       The tracker daemon command allows  for  control  of  these  components.
25       This  ranges  from  starting, stopping and killing processes to pausing
26       and resuming them.
27
28       In addition to all this, there are ways to change the log verbsity  for
29       all processes that generate logs and to follow or watch what is happen‐
30       ing in real time from a top level and right down where the SPARQL  com‐
31       mits are happening too.
32
33       If  no arguments are provided this command will show the current status
34       of all Tracker entities (store and all available data miners).
35
36       For tracker-store, the status is always "Idle" unless it is restoring a
37       backup  and/or replaying a journal (see also tracker reset --soft). For
38       a list of common statuses, see --list-common-statuses.
39
40       The data miners can be paused or resumed using this command and you can
41       also list miners running and available.
42
43

OPTIONS

45       -p, --list-processes
46              This lists all Tracker processes in the system.
47
48       -k, --kill=[daemons]
49              This  uses  SIGKILL to stop all Tracker processes found matching
50              the parameter, if no extra parameter is passed,  "all"  will  be
51              assumed.   This  is  not  advised unless you are having problems
52              stopping Tracker in the first place. This GUARANTEES death.
53
54              The possible daemons options are:
55
56               ·   all - All daemons.
57
58               ·   store - Only the tracker-store.
59
60               ·   miners - Only data miners.
61
62
63
64       -t, --terminate=[daemons]
65              This uses SIGTERM to stop all Tracker processes  found  matching
66              the  parameter,  if  no extra parameter is passed, "all" will be
67              assumed.  This is recommended over --kill because it  gives  the
68              processes time to shutdown cleanly.
69
70              For a list of possible daemons, see --kill.
71
72       -s, --start
73              Starts  all  miners.  This  indirectly  starts tracker-store too
74              because it is needed for miners to operate properly.  The  store
75              is started from D-Bus.
76
77       --get-log-verbosity
78              This  displays  the log verbosity for ALL components using GSet‐
79              tings  for  this  configuration.  For   possible   values,   see
80              --set-log-verbosity.
81
82       --set-log-verbosity=<verbosity>
83              This  sets  the log verbosity for ALL daemons using GSettings to
84              store their "verbosity" configuration.
85
86              The possible verbosity options are:
87
88               ·   debug - Show EVERYTHING, from  debug  messages  to  errors.
89                   This often includes actual SQL being executed.
90
91               ·   detailed - Show enough detail to understand what is happen‐
92                   ing.
93
94               ·   minimal - Show an overview of what is going on, e.g.  stats
95                   and when things start or stop.
96
97               ·   errors  -  Show  only  warnings, criticals, errors or fatal
98                   events.
99
100
101       -f, --follow
102              Follow status changes to daemons as they happen. This is  a  top
103              level  view of what is happening. You will see the name for each
104              daemon and a state with the progress in that state.
105
106              This requires Ctrl+C to stop and return  to  the  command  line.
107              Each new status is put on a new line.
108
109
110       -w, --watch=[ontology]
111              Watch  changes  that  happen  to the database in real time. This
112              requires Ctrl+C to stop and return to the command line.
113
114              If ontology is unspecified, all updates are shown. The  ontology
115              can be a comma separated list of shorthand or long hand ontology
116              properties. For example:
117
118                  $ tracker-control -w nie:url,nie:mimeType,nfo:fileSize,nie:dataSource
119                  Now listening for resource updates to the database
120                  All nie:plainTextContent properties are omitted
121
122                  Press Ctrl+C to stop
123
124                  'nfo:Document'
125                     'nfo:fileSize' = '1770'
126                     'nie:dataSource' = 'http://www.tracker-project.org/ontologies/tracker#extractor-data-source'
127                     'nie:mimeType' = 'text/plain'
128                     'nie:url' = 'file:///home/martyn/.bash_aliases'
129                  'nfo:Document'
130                     'nie:dataSource' = 'http://www.tracker-project.org/ontologies/tracker#extractor-data-source'
131
132                  ...
133
134
135       --list-common-statuses
136              This will list statuses most commonly produced by miners and the
137              store.  These  statuses  are not translated when sent over D-Bus
138              and should be translated by each application. These are not con‐
139              sidered static and are subject to change at any point.
140
141              Additionally,  these statuses are not the only ones which may be
142              reported by a miner. There may be other states pertaining to the
143              specific roles of the miner in question.
144
145       --list-miners-running
146              This  will list all miners which have responded to a D-Bus call.
147              Sometimes it is helpful to use  this  command  with  --list-min‐
148              ers-available.
149
150       --list-miners-available
151              This  will  list all miners which are available even if they are
152              not running at the moment.
153
154       --pause-details
155              For listing all miners which are  paused  and  the  reasons  for
156              being  paused, you can use this. It will also display the appli‐
157              cation that requested the pause too.
158
159       --miner=<miner>
160              This argument is used with --pause  or  --resume  to  say  which
161              miner  you  want  to pause or resume. You can use the full D-Bus
162              name, e.g. "org.freedesktop.Tracker1.Miner.Files" OR you can use
163              the suffix, e.g. "Files".
164
165       --pause=<reason>
166              The  reason  here  is  useful  to  know  WHY the miner should be
167              paused. A miner can be paused many times  by  multiple  applica‐
168              tions.  Only when all pauses have been resumed will it continue.
169              If successful, a cookie will be given to uniquely  identify  the
170              request.  This  cookie  is  used  to resume the pause at a later
171              stage.
172
173       --pause-for-process=<reason>
174              This works exactly the same way as --pause  with  the  exception
175              that it only keeps the pause active while the calling process is
176              alive. As soon as you press Ctrl+C the pause is resumed automat‐
177              ically.
178
179       --resume=<cookie>
180              The  cookie  is  given  by a successful --pause command. It is a
181              number which identifies each pause request. When all pauses have
182              been resumed, the miner will resume working.
183
184

ENVIRONMENT

186       TRACKER_MINERS_DIR
187              Miners  that  are  installed  should  have  a  .desktop  file in
188              /usr/share/tracker/miners/, this is  how  tracker-control  knows
189              about miners which exist but may not have not been started. This
190              environment variable allows the  location  that  miner  .desktop
191              files  are  loaded  from to be overridden by setting it to a new
192              path.
193
194       TRACKER_MINERS_DIR_DISABLED
195              If you don't have .desktop files for miners, you  can  use  this
196              environment variable to get status information from RUNNING pro‐
197              cesses. This doesn't give any indication for miners NOT running.
198              This  uses  registered  miners  on  DBus  to know about existing
199              Tracker based data miners.
200
201

SEE ALSO

203       tracker-store(1).
204
205
206
207GNU                             September 2014               tracker-daemon(1)
Impressum