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  [ -v ] [ --debug debug configuration ] [ -H host ] [
11       -P port ] [ -T protocol ] [ -C certificate ] [ -n name ] [  -D  ]  man‐
12       ager.xml [flow1.xml flow2.xml ...]
13
14

DESCRIPTION

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

OPTIONS

34       -h, --help
35              Show a brief help message, then exit.
36
37       --version
38              Show the version number.
39
40       -v, --verbose
41              Be  verbose in console output. This is equivalent to setting the
42              debug level to 3, and will override any debug specifiers.
43
44       -dDEBUG, --debug=DEBUG
45              Set the debug configuration to the specified debug  string.  See
46              the Debugging section for details of this.
47
48       -HHOST, --hostname=HOST
49              Specify  the  interface  to  bind  to, either as a hostname or a
50              numeric address.  Usually, unless you have multiple network con‐
51              nections, you won't want to set this at all. Defaults to binding
52              to all interfaces.
53
54       -PPORT, --port=PORT
55              Set the port the manager should listen on. Default  is  7531  if
56              SSL is being used, or 8642 otherwise.
57
58       -TTRANSPORT, --transport=TRANSPORT
59              Set  the  transport  protocol  to  use,  either  'tcp' or 'ssl'.
60              Default is 'ssl'.
61
62       -CCERTIFICATE, --certificate=CERTIFICATE
63              Specify the PEM certificate file to use. This is required if you
64              use SSL.
65
66       -nNAME, --name=NAME
67              Set the manager name.
68
69       -D, --daemonize
70              Run in the background as a daemon.
71
72

DEBUGGING

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

EXAMPLES

103       Simple example, starting flumotion-manager using TCP, in verbose mode:
104
105              flumotion-manager -v -T tcp conf/managers/default/planet.xml
106
107       A slightly more complex  example,  using  two  different  configuration
108       files and running in the background:
109
110              flumotion-manager  -T  tcp  -D  conf/managers/default/planet.xml
111              conf/managers/mystream.xml
112
113

BUGS

115       Hopefully  none.  If  you  find  any  bugs,  please  report   them   at
116       https://core.fluendo.com/trac/cgi-bin/trac.cgi
117
118