flumotion-manager(1)

1flumotion-manager(1)               Flumotion              flumotion-manager(1)
2
3
4

NAME

6       flumotion-manager - streaming media server central management
7
8

SYNOPSIS

10       flumotion-manager [ - ] [ --debug debug configuration ] [ -L logdir ] [
11       -R rundir ] [ -H host ] [ -P port ] [ -T protocol ] [ -C certificate  ]
12       [ -n name ] [ -s servicename ] [ -D ] [ --daemonize-to=directory ] man‐
13       ager.xml [flow1.xml flow2.xml ...]
14
15

DESCRIPTION

17       flumotion-manager is the central management component of the  flumotion
18       streaming  server.   flumotion-manager  does  not  actually perform any
19       streaming or encoding itself, it simply acts as  a  central  point  for
20       flumotion-worker  instances and flumotion-admin administration consoles
21       to connect to. You need to start it before any other  flumotion  compo‐
22       nent.  When  starting flumotion-manager, you need only specify a planet
23       configuration file , but it is frequently helpful to set other  options
24       from the command line.
25
26       flumotion-manager  can  load other configuration files as well, if more
27       than one is specified.  These  additional  configuration  files  define
28       flows  that  the  manager  will  run on the workers. This allows you to
29       define your manager configuration in the first configuration file,  and
30       your  streaming  configuration  or  configurations in one or more addi‐
31       tional configurations files.
32
33

OPTIONS

35       -h, --help
36              Show a brief help message, then exit.
37
38       --version
39              Show the version number.
40
41       -v, --verbose
42              Be verbose in console output. This is equivalent to setting  the
43              debug level to 3, and will override any debug specifiers.
44
45       -dDEBUG, --debug=DEBUG
46              Set  the  debug configuration to the specified debug string. See
47              the Debugging section for details of this.
48
49       -L LOGDIR, --logdir=LOGDIR
50              Specify the directory for logging output from the manager.
51
52       -R RUNDIR, --rundir=RUNDIR
53              Specify the directory for runtime files created by the manager.
54
55       -HHOST, --hostname=HOST
56              Specify the interface to bind to, either  as  a  hostname  or  a
57              numeric address.  Usually, unless you have multiple network con‐
58              nections, you won't want to set this at all. Defaults to binding
59              to all interfaces.
60
61       -PPORT, --port=PORT
62              Set  the  port  the manager should listen on. Default is 7531 if
63              SSL is being used, or 8642 otherwise.
64
65       -TTRANSPORT, --transport=TRANSPORT
66              Set the transport  protocol  to  use,  either  'tcp'  or  'ssl'.
67              Default is 'ssl'.
68
69       -CCERTIFICATE, --certificate=CERTIFICATE
70              Specify the PEM certificate file to use. This is required if you
71              use SSL.
72
73       -nNAME, --name=NAME
74              Set the manager name.
75
76       -sSERVICENAME, --service-name=SERVICENAME
77              Set the name used for naming log and pid files when running as a
78              daemon.
79
80       -D, --daemonize
81              Run in the background as a daemon.
82
83       --daemonize-to=DAEMONIZETO
84              Specify what directory to run from when daemonizing.
85
86

DEBUGGING

88       In  the unlikely event of something in flumotion not working, you might
89       want to debug it. The flumotion tools ( flumotion-worker  ,  flumotion-
90       admin , and flumotion-manager ) all allow you to turn on debugging out‐
91       put in two different ways.
92
93       Firstly, you can use an environment variable, FLU_DEBUG. Secondly,  you
94       can  launch  the  program  with a -d or --debug switch. Either approach
95       allows you to specify a debug configuration string with  the  following
96       syntax:
97
98              name1:n1,name2:n2,name3:n3
99
100       In this syntax, the 'name' variables can be replaced with the name of a
101       particular module within flumotion (such as 'admin', 'twisted',  etc.).
102       You can also use '*' to specify all modules. The 'n' variables are num‐
103       bers from 1 to 5, larger numbers corresponding to more  verbose  output
104       (ERROR,  WARN, INFO, DEBUG, and LOG). At level 4, full debugging infor‐
105       mation is emitted.
106
107       You can also use an abbreviated form where you  just  supply  a  single
108       number,  thisuses  that  debug level for all modules. Thus the simplest
109       way to enable full debug output for all modules is to use '-d 4' on the
110       command line.
111
112       A  more  complex  example  would be '-d *:3,admin:4' to set the logging
113       level for the admin module to DEBUG, and for all other modules to INFO.
114
115

EXAMPLES

117       Simple example, starting flumotion-manager using TCP, in verbose mode:
118
119              flumotion-manager -v -T tcp conf/managers/default/planet.xml
120
121       A slightly more complex  example,  using  two  different  configuration
122       files and running in the background:
123
124              flumotion-manager  -T  tcp  -D  conf/managers/default/planet.xml
125              conf/managers/mystream.xml
126
127

BUGS

129       Hopefully  none.  If  you  find  any  bugs,  please  report   them   at
130       https://core.fluendo.com/trac/cgi-bin/trac.cgi
131
132