Getting MediaTomb to run in daemon mode can be a bit fiddly as it's not always clear where the configuration is being read from (this will often result in your media library and all settings being blown away!).

+

+

=== Auto Start for ipkg Installs ===

+

The current ipkg package provides an init script with some additional configuration. To enable automatic startup of the MediaTomb daemon edit /opt/etc/default/mediatomb and change the value of MT_ENABLE to true. After that start the daemon by issuing the following command:

+

/opt/etc/init.d/S90mediatomb start

+

+

In this configuration MediaTomb will listen on port 50500, this behavior can be changed by editing ''/opt/etc/mediatomb.conf'' and restarting the server which can by done by:

+

/opt/etc/init.d/S90mediatomb restart

+

+

The config.xml and the database of the daemon configuration will be created in /opt/etc/mediatomb after the first launch. If you encounter strange behavior or are not sure what is going on, have a look at the log output which will be located in ''/opt/var/log/mediatomb''

+

+

=== Auto Start when compiled from source ===

+

The easiest way to get MediaTomb to start on boot is to create an init.d script; here's one I rolled earlier - all the configuration goes at the top.

Create this file in ''/etc/init.d/mediatomb'' and then make it executable via:

+

chmod +X /etc/init.d/mediatomb

+

+

Next you need to create a symlink in the appropriate rc.d folder which will cause this script to be executed as the system starts up:

+

ln -s /etc/init.d/mediatomb /etc/rc.d/rcS.d/S99mediatomb

+

+

The next time you start your system, MediaTomb should automagically wind up, if it doesn't the first place to look is the log file which should have been created over at:

+

/var/log/mediatomb.log

+

+

+

== Common Problems ==

+

=== MediaTomb fails to start with a -203 uPNP Error ===

+

If you are seeing the following in your log output:

+

2009-04-14 21:54:37 ERROR: main: upnp error -203

+

2009-04-14 21:54:37 ERROR: Could not bind to socket.

+

2009-04-14 21:54:37 INFO: Please check if another instance of MediaTomb or

+

2009-04-14 21:54:37 INFO: another application is running on the same port.

+

+

Then it's very likley that you have another uPNP server running on your machine; the most likely candidate is the PCCast daemon which is found on the OpenLink; you can stop it from starting up by modifying:

Overview

MediaTomb is an open source (GPL) UPnP MediaServer with a nice web user interface, it allows you to stream your digital media through your home network and listen to/watch it on a variety of UPnP compatible devices.

MediaTomb implements the UPnP MediaServer V 1.0 specification that can be found on http://www.upnp.org/.

OpenLink (MIPSEL)

and find the appropriate file for your linkstation under the static binaries area. For the linkstation 2 it is mediatomb-static-0.11.0-r2-linux-uclibc-mips2el.tar.gz.
at the command prompt on your linkstation go somewhere to store the file:

Compiling from source

Usage Options

Usage: mediatomb [options]

Supported options:
--ip or -i ip address
--port or -p server port (the SDK only permits values => 49152)
--config or -c configuration file to use
--daemon or -d run server in background
--pidfile or -P file to hold the process id
--user or -u run server under specified username
--group or -g run server under specified group
--add or -a add the given file/directory
--logfile or -l log to specified file
--help or -h this help message

Starting MediaTomb on Boot

Getting MediaTomb to run in daemon mode can be a bit fiddly as it's not always clear where the configuration is being read from (this will often result in your media library and all settings being blown away!).

Auto Start for ipkg Installs

The current ipkg package provides an init script with some additional configuration. To enable automatic startup of the MediaTomb daemon edit /opt/etc/default/mediatomb and change the value of MT_ENABLE to true. After that start the daemon by issuing the following command:

/opt/etc/init.d/S90mediatomb start

In this configuration MediaTomb will listen on port 50500, this behavior can be changed by editing /opt/etc/mediatomb.conf and restarting the server which can by done by:

/opt/etc/init.d/S90mediatomb restart

The config.xml and the database of the daemon configuration will be created in /opt/etc/mediatomb after the first launch. If you encounter strange behavior or are not sure what is going on, have a look at the log output which will be located in /opt/var/log/mediatomb

Auto Start when compiled from source

The easiest way to get MediaTomb to start on boot is to create an init.d script; here's one I rolled earlier - all the configuration goes at the top.

Create this file in /etc/init.d/mediatomb and then make it executable via:

chmod +X /etc/init.d/mediatomb

Next you need to create a symlink in the appropriate rc.d folder which will cause this script to be executed as the system starts up:

ln -s /etc/init.d/mediatomb /etc/rc.d/rcS.d/S99mediatomb

The next time you start your system, MediaTomb should automagically wind up, if it doesn't the first place to look is the log file which should have been created over at:

/var/log/mediatomb.log

Common Problems

MediaTomb fails to start with a -203 uPNP Error

If you are seeing the following in your log output:

2009-04-14 21:54:37 ERROR: main: upnp error -203
2009-04-14 21:54:37 ERROR: Could not bind to socket.
2009-04-14 21:54:37 INFO: Please check if another instance of MediaTomb or
2009-04-14 21:54:37 INFO: another application is running on the same port.

Then it's very likley that you have another uPNP server running on your machine; the most likely candidate is the PCCast daemon which is found on the OpenLink; you can stop it from starting up by modifying: