mm-detect command line

Start the multimedia device detection service


    mm-detect [-d database_path] [-i schema_data_file] 
        [-s schema_file] [-p notify_path] [-b] [-n priority] [-v] 


-d database_path
Specify an overridden directory location for storing the media metadata databases.
The default is /db/.
-i schema_data_file
Name the file (with an absolute path) that defines the initial data to store in each media metadata database. This text file contains the SQL commands to populate a database when it's created, which happens when the device is inserted for the first time. Note that this option is processed only if the -s option is set to use a schema creation file.
The default is /db/mmsync_data_car2.sql.
-s schema_file
Name the file (with an absolute path) containing the SQL commands that create the initial schema of tables, indexes, and views of each media metadata database. The schema file is used only to set up the database when the device is inserted for the first time (i.e., the database didn't already exist).
The default is /db/mmsync_car2.sql.
-p notify_path
Specify an overridden directory location for storing the PPS object used to notify the car's HMI of synchronization status updates.
The default is /pps/services/mm-detect/.
Run the mm-detect process in the foreground. This option is handy for debugging, because it makes mm-detect log messages to standard error in addition to sloginfo.
By default, mm-detect runs in the background.
-n priority
Set the priority of the mm-detect process. When your system is busy running many applications, the priority level can have a considerable impact on the time to see up-to-date media information after a device is inserted.
The valid range is 1 to 63; the default is 15.
Increase output verbosity. Messages are written to sloginfo. The -v option is cumulative, so you can add several v's to increase verbosity, up to four levels.
Output verbosity is handy when you're trying to understand the operation of mm-detect. However, when lots of -v arguments are used, the logging becomes quite significant and can change timing noticeably. The verbosity setting is good for systems under development but probably shouldn't be used in production systems or during performance testing.


The mm-detect command starts the multimedia detection service, which continuously monitors device attachments. Each time a device is attached, the service invokes mm-sync to synchronize the device's media metadata with the appropriate QDB database, and then publishes synchronization updates through PPS to the HMI.

Through command options, you can set new locations for storing the PPS synchronization objects, media databases, or the files containing the schemas used to create and initialize those databases. You can further control mm-detect by setting the command-line options for the process priority and the debugging output level.

The mm-detect service runs as a self-contained process that doesn't require any user input or accept any commands. It has no client utility for performing specific device-monitoring tasks on request or for adjusting any of the previously mentioned settings. To reconfigure mm-detect, you must change the options in its command line. In CAR systems, this command line is contained in the SLM configuration file, located at /etc/slm-config-all.xml.