mme-generic

MME resource manager

Syntax:

mme
[-c config_file] [-o logging=level:flags] [-DFSv]

Runs on:

ARM, PowerPC, SH, x86

Options:

-c config_file
Load the specified configuration file; see below.
-D
Print messages sent to the system log to the standard output. Using the -v option to set the verbosity level.
-F
Stay in the foreground. By default, mme-generic is spawned into a different process. When it is in the foreground, you can use ctrl-c to kill it.
-o logging=module@level:flags
Set the logging verbosity levels for the specified modules. See Setting log verbosity levels below.
-S
Log synchronization statistics to dev/slog.
-v
Turn on verbose mode. In this mode, messages about MME activity are sent to the system log. Increase the number of vs to increase the verbosity. Use the -D option to also view the messages on the standard output.
-V
Print to stderr the schema versions mme expects and the schema versions it finds. See Checking schema versions below.

Description:

The mme-generic is a resource manager that handles device discovery and synchronization. It also provides the high-level API for managing playback (play, stop, and seek commands), and manages the library database.

Before you start mme-generic, your target must also be running:

See also the chapter MME Quickstart Guide in the Introduction to the MME.

Configuration File

You can start mme-generic with a configuration file to change its default behavior. To create a configuration file, you should edit the sample mme.conf file provided with the MME. This is a self-documented XML file, with all possible parameters commented out, so you can un-comment and modify the parameters you wish to change.

For more information about configuring mme-generic, see the MME Configuration Guide.

Checking schema versions

At startup, mme checks the schema versions installed and compares these to the versions it requires:

Finding out the schema versions mme expects

You can use the -V option to find out the schema versions mme expects — afer an upgrade, for example. If you use the -V when starting it, mme just prints to stderr and exits. Correct schema versions produce a response like:

# mme-generic -V
Database Schema versions expected
File:mme.sql Database:main expected:16
File:mme_library.sql Database:mme_library expected:4
File:mme_temp.sql Database:mme_temp expected:4

Setting log verbosity levels

The -o option can be used to set logging verbosity levels for specified mme modules. It can be used to set, for example, a lower verbosity for synchronizations than for the rest of the MME so that, when detailed logging is required to debug or fine-tune some other feature, the writing of synchronization logs for large mediastores does not increase synchronization times.

Specify the logging module, the logging verbosity level and the logging flags for each module separately, separating the options for the different modules with semi-colons. For example:

# mme-generic -c $QNX_TARGET/etc/mme.conf -o logging="sync@2:0;mdi@2:1;mdp@2:0"

Logging modules

The strings that identify mme logging modules include:


Note: The above list is not definitive. The logging modules may change. To find out what logging module strings are valid, call mme_get_logging() with the string referenced by the name argument set to NULL.

Logging flags

The logging flags are bit masks that configure logging behavior:


Note: Log verbosity levels can be retrieved and set with the mme_get_logging.html() and mme_set_logging.html() functions.

Files:

/db/*.sql
Supporting schema files for databases created by qdb
mme.conf
Sample configuration file.

See also:

mmecli