Appendix D. Command-line Options

Table of Contents

Starting the manager

You may start a flumotion Manager with the flumotion-manager command, and then use ps to check that it is up and running. For instance:

[root@server root]# flumotion-manager -d 3 path/to/planet.xml 2> manager.log &
[root@server root]# ps -ef|grep flumotion-manager
root 7188 7148 1 18:24 pts/2 00:00:01 /usr/bin/python /usr/bin/flumotion-manager 

This command does four things:

  • It starts the manager with logging output. All informational, warning and error messages will be output.

  • It starts the manager with the configuration as specified in planet.xml. An example configuration file is included with the source distribution.

    This file describes the configuration of the planet to be managed. Among other things, this specifies the authentication information for components logging in to the manager. [5]

  • All output is redirected to a manager.log log file. This allows you to see all the log messages the manager generates using a standard text viewer.

  • The manager process is started in the background using &.

[5] Many other parameters are available when starting the manager. These include options to specify the communication protocol, the port to listen on, the host to listen as, etc. For a list of these options, run the flumotion-manager -h command.

Some of these options can also be specified in the planet.xml file with which the manager is started.