Linux Manuals session 1

trademgen_extractBookingRequests – Script extracting booking requests, as generated by the C++ Simulated Travel Demand Generation (TraDemGen) LibrarySynopsistrademgen_extractBookingRequests [-h|–help] [-i|–input <path-to-input-log-file> Descriptiontrademgen_extractBookingRequests is a small shell script, extracting the booking requests from the log file produced by the ‘trademgen_generateDemand’ binary. It produces an output with the following format: Logfile line number, Booking date, Orign-Destination, Departure date…

trademgen_drawBookingArrivals – Script plotting booking arrival curves, as generated by the C++ Simulated Travel Demand Generation (TraDemGen) LibrarySynopsistrademgen_drawBookingArrivals [-h|–help] [-o|–output <path-to-output-file>] [-p|–plot] <path-to-input-log-file> Descriptiontrademgen_drawBookingArrivals is a small Python script, extracting the booking requests from the log file produced by the trademgen_generateDemand binary. It produces booking curves, which can even be rendered by a simple Matplotlib…

NAME trademgen – Interactive command-line utility for the C++ Simulated Travel Demand Generation Library SYNOPSIS trademgen [–prefix] [-v|–version] [-h|–help] [-b|–builtin] [-i|–input <path-to-input>] [-l|–log <path-to-output-log-file>] DESCRIPTION trademgen is a small interactive program showing how to use the TraDemGen library. trademgen accepts the following options: –prefix  Show the TraDemGen installation prefix. -v, –version  Print the currently installed…

NAME trademgen-config – Configuration Script for the C++ Simulated Travel Demand Generation Library SYNOPSIS trademgen-config [–prefix] [–version] [–libs] [–cflags] DESCRIPTION trademgen-config is a tool that is used by configure to determine the compiler and linker flags that should be used to compile and link programs that use TraDemGen. It is also used internally by the…

NAME tracker3-tag – Add, remove and list tags. SYNOPSIS tracker3 tag FILE1[FILE2…][-l<limit>][-o<offset>][-r] tracker3 tag – t [[TAG1] [TAG2]…][-s][-r] tracker3 tag – a<TAG>[-e<description>] tracker3 tag – d<TAG> DESCRIPTION List tags for local files or by the tag labels themselves if -t is used. It’s also possible to manage tags with the -a and and -d options….

NAME tracker3-status – Provide status and statistics on the data indexed SYNOPSIS tracker3 status tracker3 status [[expression1]…] tracker3 status– stat[-a] [[expression1]…] DESCRIPTION Display the status of the current index and data set. A summary of recorded failures during file metadata indexing is also displayed. Providing a search expression will list the full details of the…

NAME tracker3-sql – Use SQL to query the Tracker databases. SYNOPSIS tracker3 sql -q <sql> | -f <file> DESCRIPTION This command allows probing of the current database. When using commands like tracker3 sparql, the SPARQL used is translated into SQL before being run on the database. This allows direct use of the database using SQL…

NAME tracker3-sparql – Use SparQL to query the Tracker databases. SYNOPSIS tracker3 sparql – q<sparql>[-u] | -f<file> tracker3 sparql – t[class][-s<needle>][-p] tracker3 sparql[-c][-p][-x][-n[class]][-i[property]][-s<needle>] tracker3 sparql[–get – longhand<class>][–get – shorthand<class>] DESCRIPTION This command allows probing of the current database schema (also known as ontology) and running low level queries or updates on the data set. In…

NAME tracker3-search – Search for content by type or across all types SYNOPSIS tracker3 search [options…] [[expression1] …] DESCRIPTION tracker3 search searches all indexed content for expression. The resource in which expression matches must exist (see –all for more information). All results are returned in ascending order. In all cases, if no expression is given…

NAME tracker3-reset – Reset the index and configuration SYNOPSIS tracker3 reset [–filesystem | –rss] [–file FILE] DESCRIPTION The reset command will change either your configuration or index irreversibly and should be used with care. Other than tags, actual data (e.g. files) should not be affected by this command. The "index" is a link between your…

NAME tracker3-info – Retrieve all information available for a certain file. SYNOPSIS tracker3 info [options…] <file1> [[file2] …] DESCRIPTION tracker3 info asks for all the known metadata available for the given file. Multiple file arguments can be provided to retrieve information about multiple files. The file argument can be either a local path or a…

NAME tracker3-index – Index content using the Tracker filesystem miner SYNOPSIS tracker3 index tracker3 index– add[–recursive]<dir> [[dir]…] tracker3 index– remove<path> [[dir]…] DESCRIPTION This command causes the Tracker filesystem miner to process the given directories. These changes are persistent across future restarts. If invoked without arguments, the currently indexed locations will be listed. SEE ALSO tracker-miner-fs-3(1)….

NAME tracker3-import – Import data into a Tracker database. SYNOPSIS tracker3 import FILE.ttl DESCRIPTION tracker3 import imports data into a Tracker database. The data must conform to the existing ontology of the database. The data must be in Turtle format. You can use a tool such as rapper(1) to convert the data from other formats…

NAME tracker3-extract – Extract metadata from a file. SYNOPSYS tracker3 extract FILE DESCRIPTION tracker3 extract reads the file provided and extracts any metadata it can from this file, then displays the metadata on standard output. The metadata is displayed as a SPARQL update command, that can be run against a SPARQL endpoint to update its…

NAME tracker3-export – Export all data from a Tracker database. SYNOPSIS tracker3 export [options…] [IRI…] DESCRIPTION tracker3 export exports data stored in a Tracker database, in Turtle format. By default all data is exported, if any IRI, only those resources will be printed. The output is intended to be machine-readable, not human readable. Use a…

NAME tracker3-endpoint – Create a SPARQL endpoint SYNOPSIS tracker3 endpoint[–dbus – service | -b]<service_name>[–database – path | -d]<database_path>[[–ontology | -o]<ontology_name> | [–ontology – path | -p]<ontology_path>] [–http – port]<port>[–loopback] [[–system | –session]] DESCRIPTION This command allows creating SPARQL endpoints. The endpoint will be able to handle SPARQL select and update queries, and notify about changes…

NAME tracker3-daemon – Start, stop, restart and list daemons responsible for indexing content SYNOPSIS tracker3 daemon [options…] tracker3 daemon -s | -t [daemons] | -k [daemons] | -l tracker3 daemon -f | -w [ontology] tracker3 daemon –miner <miner> –pause[-for-process] <reason> tracker3 daemon –miner <miner> –resume <cookie> DESCRIPTION Tracker indexes content with daemon processes that run…

NAME tracker-xdg-portal-3 – Portal to Tracker endpoints SYNOPSIS tracker-xdg-portal-3 [–version | -v] DESCRIPTION This daemon allows access to Tracker endpoints in a controlled manner. By default access to every service is disallowed, services may be whitelisted through additional policy in the .flatpak-info file. When whitelisting services, the policy may define specific graph names to allow…

NAME tracker-writeback – Used to write metadata set in Tracker back to physical files. SYNOPSIS tracker-writeback [OPTION…] DESCRIPTION tracker-writeback is not supposed to be run by the user since it is started by its .desktop file when the user logs in. It can also be started manually of course for debugging purposes. You can not…

NAME tracker-writeback-3 – Used to write metadata set in Tracker back to physical files. SYNOPSIS tracker-writeback [OPTION…] DESCRIPTION tracker-writeback is not supposed to be run by the user since it is started by its .desktop file when the user logs in. It can also be started manually of course for debugging purposes. You can not…