tracker-extract(1) [centos man page]

tracker-extract(1)						   User Commands						tracker-extract(1)

NAME

       tracker-extract - Extract metadata from a file.

SYNOPSYS

       tracker-extract [OPTION...] FILE...

DESCRIPTION

       tracker-extract reads the file and mimetype provided in stdin and extract the metadata from this file; then it displays the metadata on the
       standard output.

       NOTE: If a FILE is not provided then tracker-extract will run for 30 seconds waiting for DBus calls before quitting.

OPTIONS

       -?, --help
	      Show summary of options.

       -v, --verbosity=N
	      Set verbosity to N. This overrides the config value.  Values include 0=errors, 1=minimal, 2=detailed and 3=debug.

       -f, --file=FILE
	      The FILE to extract metadata from. The FILE argument can be either a local path or a URI. It also does not have to  be  an  absolute
	      path.

       -m, --mime=MIME
	      The MIME type to use for the file. If one is not provided, it will be guessed automatically.

       -d, --disable-shutdown
	      Disable shutting down after 30 seconds of inactivity.

       -i, --force-internal-extractors
	      Use this option to force internal extractors over 3rd parties like libstreamanalyzer.

       -m, --force-module=MODULE
	      Force  a particular module to be used. This is here as a convenience for developers wanting to test their MODULE file. Only the MOD-
	      ULE name has to be specified, not the full path. Typically, a MODULE is installed  to  /usr/lib/tracker-0.7/extract-modules/.   This
	      option can be used with or without the .so part of the name too, for example, you can use --force-module=foo

	      Modules are shared objects which are dynamically loaded at run time. These files must have the .so suffix to be loaded and must con-
	      tain the correct symbols to be authenticated by tracker-extract.	For more information see the libtracker-extract reference documen-
	      tation.

       -V, --version
	      Show binary version.

EXAMPLES

       Using command line to extract metadata from a file:

	       $ tracker-extract -v 3 -f /path/to/some/file.mp3

       Using a specific module to extract metadata from a file:

	       $ tracker-extract -v 3 -f /path/to/some/file.mp3 -m mymodule

ENVIRONMENT

       TRACKER_EXTRACTORS_DIR
	      This  is	the directory which tracker uses to load the shared libraries from (used for extracting metadata for specific file types).
	      These are needed on each invocation of tracker-store. If unset it will default to the correct place. This is used mainly for testing
	      purposes. The default location is /usr/lib/tracker-0.10/extract-modules/.

       TRACKER_EXTRACTOR_RULES_DIR
	      This  is	the  directory which tracker uses to load the rules files from.  The rules files describe extractor modules and their sup-
	      ported MIME types. The default location is /usr/share/tracker/extract-rules/.

       TRACKER_USE_CONFIG_FILES
	      Don't use GSettings, instead use a config file similar to how settings were saved in 0.10.x. That is, a file which is much  like	an
	      .ini file.  These are saved to $HOME/.config/tracker/

SEE ALSO

       tracker-store(1), tracker-sparql(1), tracker-stats(1), tracker-info(1).

       /usr/lib/tracker-0.10/extract-modules/

       /usr/share/tracker/extract-rules/

GNU
								     July 2007							tracker-extract(1)

Check Out this Related Man Page

tracker-status(1)						   User Commands						 tracker-status(1)

NAME

       tracker-status - Report the state of all data miners

SYNOPSIS

       tracker-status [OPTION...]

DESCRIPTION

       tracker-status  shows  the status of all miners installed. It also allows pausing and resuming of miners. For tracker-store state, you need
       to use tracker-control

OPTIONS

       -?, --help
	      Show summary of options.

       -f, --follow
	      Follow status changes as they happen. This requires Ctrl+C to stop and return to the command line. Each new status is put on  a  new
	      line. To get more information, you can use --detailed with this.

       -d, --detailed
	      For the most part, this purely provides a timestamp with each status update to follow WHEN changes happened.

       -s, --list-common-statuses
	      This  will  list statuses most commonly produced by miners and the store. These statuses are not translated when sent over D-Bus and
	      should be translated by each application. These are not considered static and are subject to change at any point.

	      Additionally, these statuses are not the only ones which may be reported by a miner. There may be other  states  pertaining  to  the
	      specific roles of the miner in question.

       -l, --list-miners-running
	      This  will  list	all miners which have responded to a D-Bus call.  Sometimes it is helpfult to use this command with --list-miners-
	      available.

       -a, --list-miners-available
	      This will list all miners which are available even if they are not running at the moment.

       -i, --pause-details
	      For listing all miners which are paused and the reasons for being paused, you can use this. It will  also  display  the  application
	      that requested the pause too.

       -m, --miner=MINER
	      This  argument  is  used	with --pause and --resume to say which miner you want to pause or resume. You can use the full D-Bus name,
	      e.g.  org.freedesktop.Tracker1.Miner.Files OR you can use the suffix, e.g.  Files

       -p, --pause=REASON
	      The REASON here is useful to know WHY the miner should be paused. A miner can be paused many times by  multiple  applications.  Only
	      when  all  pauses  have  been resumed will it continue. If successful, a cookie will be given to uniquely identify the request. This
	      cookie is used to resume the pause at a later stage.

       -r, --resume=COOKIE
	      The COOKIE is given by a successful --pause command. It is a number which identifies each pause request. When all pauses	have  been
	      resumed, the miner will resume working.

       -V, --version
	      Print version.

SEE ALSO

       tracker-store(1), tracker-stats(1), tracker-control(1)

GNU
								     July 2009							 tracker-status(1)

Linux and UNIX Man Pages

tracker-extract(1) [centos man page]

Check Out this Related Man Page