1TRACKER3-DAEMON(1)              Tracker manual              TRACKER3-DAEMON(1)
2
3
4

NAME

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

SYNOPSIS

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

DESCRIPTION

17       Tracker indexes content with daemon processes that run in the
18       background. The tracker3 daemon command allows for control of these
19       components. This ranges from starting, stopping and killing processes
20       to pausing and resuming them.
21
22       In addition to all this, there are ways to follow or watch what is
23       happening in real time from a top level and right down where the SPARQL
24       commits are happening too.
25
26       If no arguments are provided this command will show the current status
27       of all Tracker data miners.
28
29       The data miners can be paused or resumed using this command and you can
30       also list miners running and available.
31

OPTIONS

33       -p, --list-processes
34           This lists all Tracker processes in the system.
35
36       *-k, --kill
37           This uses SIGKILL to stop all Tracker processes found matching the
38           parameter, if no extra parameter is passed, "all" will be assumed.
39           This is not advised unless you are having problems stopping Tracker
40           in the first place. This GUARANTEES death.
41
42       *-t, --terminate=
43           This uses SIGTERM to stop all Tracker processes. This is
44           recommended over --kill because it gives the processes time to
45           shutdown cleanly.
46
47       -s, --start
48           Starts all miners.
49
50       -f, --follow
51           Follow status changes to daemons as they happen. This is a top
52           level view of what is happening. You will see the name for each
53           daemon and a state with the progress in that state.
54
55       This requires Ctrl+C to stop and return to the command line. Each new
56       status is put on a new line.
57
58       -w, --watch=[ontology]
59           Watch changes that happen to the database in real time. This
60           requires Ctrl+C to stop and return to the command line.
61
62       If ontology is unspecified, all updates are shown. The ontology can be
63       a comma separated list of shorthand or long hand ontology properties.
64       For example:
65
66               $ tracker3 daemon -w nie:url,nie:mimeType,nfo:fileSize,nie:dataSource
67               Now listening for resource updates to the database
68               All nie:plainTextContent properties are omitted
69
70               Press Ctrl+C to stop
71
72               'nfo:Document'
73                  'nfo:fileSize' = '1770'
74                  'nie:dataSource' = 'http://tracker.api.gnome.org/ontology/v3/tracker#extractor-data-source'
75                  'nie:mimeType' = 'text/plain'
76                  'nie:url' = 'file:///home/martyn/.bash_aliases'
77               'nfo:Document'
78                  'nie:dataSource' = 'http://tracker.api.gnome.org/ontology/v3/tracker#extractor-data-source'
79
80               ...
81
82       --list-common-statuses
83           This will list statuses most commonly produced by miners and the
84           store. These statuses are not translated when sent over D-Bus and
85           should be translated by each application. These are not considered
86           static and are subject to change at any point.
87
88       Additionally, these statuses are not the only ones which may be
89       reported by a miner. There may be other states pertaining to the
90       specific roles of the miner in question.
91
92       --list-miners-running
93           This will list all miners which have responded to a D-Bus call.
94           Sometimes it is helpful to use this command with
95           --list-miners-available.
96
97       --list-miners-available
98           This will list all miners which are available even if they are not
99           running at the moment.
100
101       --pause-details
102           For listing all miners which are paused and the reasons for being
103           paused, you can use this. It will also display the application that
104           requested the pause too.
105
106       --miner=<miner>
107           This argument is used with --pause or --resume to say which miner
108           you want to pause or resume. You can use the full D-Bus name, e.g.
109           "org.freedesktop.Tracker3.Miner.Files" OR you can use the suffix,
110           e.g. "Files".
111
112       --pause=<reason>
113           The reason here is useful to know WHY the miner should be paused. A
114           miner can be paused many times by multiple applications. Only when
115           all pauses have been resumed will it continue. If successful, a
116           cookie will be given to uniquely identify the request. This cookie
117           is used to resume the pause at a later stage.
118
119       --pause-for-process=<reason>
120           This works exactly the same way as --pause with the exception that
121           it only keeps the pause active while the calling process is alive.
122           As soon as you press Ctrl+C the pause is resumed automatically.
123
124       --resume=<cookie>
125           The cookie is given by a successful --pause command. It is a number
126           which identifies each pause request. When all pauses have been
127           resumed, the miner will resume working.
128
129
130
131  3.3.1                           06/01/2022                TRACKER3-DAEMON(1)
Impressum