Mpd is invoked by first setting up your configuration files, and then running
mpd [ options ] [ configuration ]
configurationis supplied, then mpd looks in
mpd.conffor a matching label, and runs the corresponding commands (up to the first blank line). If
configurationis not supplied, mpd looks for the configuration named
default. If the configuration is not found, no commands are executed from
Mpd can either be run in interactive mode or in the background as a daemon. In interactive mode mpd accepts commands typed at the console.
Mpd understands the following command line options. Each option has a short, single character form, as well as an equivalent long form.
Run as a background daemon.
-d --directory dir
This option allows you to specify a different directory
for the mpd configuration files other than the default
-f --file filename
Specify an initial configuration file other than the default,
-p --pidfile filename
Mpd will open and lock
write its process ID before starting. If another mpd
process is already running, mpd will not start.
The default is
With this option, pd will attempt to kill any existing mpd
process before beginning execution. The previous process
must have written its process ID in the PID file
/var/run/mpd.pid (or the file you specify with
-s --syslog-ident ident
Mpd normally logs via
syslog(3) with the identifier
mpd. This option allows you to change that identifier.
Displays the version number of mpd and exits.
Displays a usage message and exits.
Mpd responds to the following signals while it is running:
Attempt to gracefully shut down all active connections and exit.
This signal causes mpd to initiate a connection with the first link. If mpd is already attempting to connect, this signal has no effect.
This signal has the opposite effect, namely, it causes mpd to close the first link. If the link is already in a closed state, this signal has no effect.