Table of Contents
This section describes how to setup and configure Flumotion for a real-world streaming media environment. See also the Security and Usage Scenario chapters.
You can start and stop Flumotion using the service script at /etc/init.d/flumotion. For instance, use /etc/init.d/flumotion start to start Flumotion and /etc/init.d/flumotion stop to stop it.
This script tells Flumotion to use the configuration files found in /etc/flumotion/ (see the Configuration Files section) and to write logs to /var/log/flumotion/.
Your Linux distro probably starts Flumotion using this script at startup time. If it does not then you may use your Linux distro's graphical control panel to specify that this should happen, as described here.
On Fedora Linux or Red Hat Linux you may use the Service Configuration control panel to start and stop the Flumotion service. Choose + → from your panel. If you start Flumotion in this control panel then it will be started automatically at each system start.
Fedora Linux provides the chkconfig command, which helps with the administration of the /etc/rc*.d/ directories, which specify the services that should start at boot time.
For instance, you can specify that Flumotion should start at boot time with this command, as root: /sbin/chkconfig flumotion on
you can discover whether Flumotion is already specified to start at boot time with this command, as root: /sbin/chkconfig --list flumotion
You can also use the service to start and stop Flumotion manually. For instance: /sbin/service flumotion start and /sbin/service flumotion stop
On other Linux systems, such as Ubuntu Linux, you may edit the system's startup files directly. Assuming that you have a Flumotion service script at /etc/init.d/flumotion, you can cause this to be started when the system reaches a certain run level, by adding a symlink in the appropriate rc*.d/ directory. For instance,
cd /etc/rc2.d ln -s /etc/init.d/flumotion S20flumotion