Man Linux: Main Page and Category List


       flumotion-manager - streaming media server central management


       flumotion-manager [ - ] [ --debug debug configuration ] [ -L logdir ] [
       -R rundir ] [ -H host ] [ -P port ] [ -T protocol ] [ -C certificate  ]
       [  -n  name  ]  [  -s servicename ] [ -D ] [ --daemonize-to=directory ]
       manager.xml [flow1.xml flow2.xml ...]


       flumotion-manager is the central management component of the  flumotion
       streaming  server.   flumotion-manager  does  not  actually perform any
       streaming or encoding itself, it simply acts as  a  central  point  for
       flumotion-worker  instances and flumotion-admin administration consoles
       to connect to.  You  need  to  start  it  before  any  other  flumotion
       component.  When  starting  flumotion-manager,  you need only specify a
       planet configuration file , but it is frequently helpful to  set  other
       options from the command line.

       flumotion-manager  can  load other configuration files as well, if more
       than one is specified.  These  additional  configuration  files  define
       flows  that  the  manager  will  run on the workers. This allows you to
       define your manager configuration in the first configuration file,  and
       your   streaming   configuration  or  configurations  in  one  or  more
       additional configurations files.


       -h, --help
              Show a brief help message, then exit.

              Show the version number.

       -v, --verbose
              Be verbose in console output. This is equivalent to setting  the
              debug level to 3, and will override any debug specifiers.

       -dDEBUG, --debug=DEBUG
              Set  the  debug configuration to the specified debug string. See
              the Debugging section for details of this.

       -L LOGDIR, --logdir=LOGDIR
              Specify the directory for logging output from the manager.

       -R RUNDIR, --rundir=RUNDIR
              Specify the directory for runtime files created by the  manager.

       -HHOST, --hostname=HOST
              Specify  the  interface  to  bind  to, either as a hostname or a
              numeric address.  Usually,  unless  you  have  multiple  network
              connections,  you  won't  want  to  set this at all. Defaults to
              binding to all interfaces.

       -PPORT, --port=PORT
              Set the port the manager should listen on. Default  is  7531  if
              SSL is being used, or 8642 otherwise.

       -TTRANSPORT, --transport=TRANSPORT
              Set  the  transport  protocol  to  use,  either  'tcp' or 'ssl'.
              Default is 'ssl'.

       -CCERTIFICATE, --certificate=CERTIFICATE
              Specify the PEM certificate file to use. This is required if you
              use SSL.

       -nNAME, --name=NAME
              Set the manager name.

       -sSERVICENAME, --service-name=SERVICENAME
              Set the name used for naming log and pid files when running as a

       -D, --daemonize
              Run in the background as a daemon.

              Specify what directory to run from when daemonizing.


       In the unlikely event of something in flumotion not working, you  might
       want  to  debug it. The flumotion tools ( flumotion-worker , flumotion-
       admin , and flumotion-manager ) all  alow  you  to  turn  on  debugging
       output in two different ways.

       Firstly,  you can use an environment variable, FLU_DEBUG. Secondly, you
       can launch the program with a -d or  --debug  switch.  Either  approach
       allows  you  to specify a debug configuration string with the following


       In this syntax, the 'name' variables can be replaced with the name of a
       particular  module within flumotion (such as 'admin', 'twisted', etc.).
       You can also use '*' to specify all  modules.  The  'n'  variables  are
       numbers  from  1  to  5,  larger  numbers corresponding to more verbose
       output (ERROR, WARN, INFO, DEBUG, and LOG). At level 4, full  debugging
       information is emitted.

       You  can  also  use  an abbreviated form where you just supply a single
       number, thisuses that debug level for all modules.  Thus  the  simplest
       way to enable full debug output for all modules is to use '-d 4' on the
       command line.

       A more complex example would be '-d *:3,admin:4'  to  set  the  logging
       level for the admin module to DEBUG, and for all other modules to INFO.


       Simple example, starting flumotion-manager using TCP, in verbose mode:

              flumotion-manager -v -T tcp conf/managers/default/planet.xml

       A slightly more complex  example,  using  two  different  configuration
       files and running in the background:

              flumotion-manager  -T  tcp  -D  conf/managers/default/planet.xml


       Hopefully  none.  If  you  find  any  bugs,  please  report   them   at