1flumotion-worker(1) Flumotion flumotion-worker(1)
2
6 flumotion-worker - streaming media server worker
7
10 flumotion-worker [ -v ] [ --debug debug configuration ] [ -H host ] [
11 -P port ] [ -T protocol ] [ -n name ] [ -D ] -u username -p password
12
15 flumotion-worker is the part of flumotion that actually performs all
16 the real work of encoding, streaming, etc. In a flumotion system, there
17 will be a single manager, and could be several workers running on dif‐
18 ferent systems (this is useful to distribute the load of, for instance,
19 video encoding). You need to have a minimum of one worker for flumotion
20 to function correctly.
21 You should start flumotion-manager first, then connect flumotion-worker
23 to the running manager.
24
27 -h, --help
28 Show a brief help message, then exit.
29 --version
31 Show the version number.
32 -v, --verbose
34 Be verbose in console output. This is equivalent to setting the
35 debug level to 3, and will override any debug specifiers.
36 -dDEBUG, --debug=DEBUG
38 Set the debug configuration to the specified debug string. See
39 the Debugging section for details of this.
40 -HHOST, --host=HOST
42 Specify the hostname on which the manager is running.
43 -PPORT, --port=PORT
45 Specify the port on which the manager in running (usually 7531
46 for SSL, or 8642 otherwise)
47 -TTRANSPORT, --transport=TRANSPORT
49 Set the transport protocol to use, either 'tcp' or 'ssl'.
50 Default is 'ssl'.
51 -nNAME, --name=NAME
53 Set the name for this worker to use in the manager.
54 -D, --daemonize
56 Run in the background as a daemon.
57 -u, --username
59 Specify the username to use to connect to the manager.
60 -p, --password
62 Specify the password to use to connect to the manager.
63 -FPORTS, --feederports=PORT_FROM:PORT_TO
65 Specify the range of feeder ports to use in the format 'lower-
66 upper'. These are the ports used for inter-worker communication.
67 If you have multiple workers on seperate systems (perhaps one
68 doing encoding, behind a firewall, and a second doing the
69 streaming outside the firewall), they must be able to communi‐
70 cate using this port range, so you'll have to open these ports
71 in your firewall. It is recommended that you have a range of 20
72 ports.
73
76 In the unlikely event of something in flumotion not working, you might
77 want to debug it. The flumotion tools ( flumotion-worker , flumotion-
78 admin , and flumotion-manager ) all alow you to turn on debugging out‐
79 put in two different ways.
80 Firstly, you can use an environment variable, FLU_DEBUG. Secondly, you
82 can launch the program with a -d or --debug switch. Either approach
83 allows you to specify a debug configuration string with the following
84 syntax:
85 name1:n1,name2:n2,name3:n3
87 In this syntax, the 'name' variables can be replaced with the name of a
89 particular module within flumotion (such as 'admin', 'twisted', etc.).
90 You can also use '*' to specify all modules. The 'n' variables are num‐
91 bers from 1 to 5, larger numbers corresponding to more verbose output
92 (ERROR, WARN, INFO, DEBUG, and LOG). At level 4, full debugging infor‐
93 mation is emitted.
94 You can also use an abbreviated form where you just supply a single
96 number, thisuses that debug level for all modules. Thus the simplest
97 way to enable full debug output for all modules is to use '-d 4' on the
98 command line.
99 A more complex example would be '-d *:3,admin:4' to set the logging
101 level for the admin module to DEBUG, and for all other modules to INFO.
102
105 Simple example, starting flumotion-worker connecting to a manager using
106 TCP, default host and port, and with the username 'user' and the pass‐
107 word 'test'
108 flumotion-worker -v -T tcp -u user -p test --feeder‐
110 ports=8060-8080
111
114 Hopefully none. If you find any bugs, please report them at
115 https://core.fluendo.com/trac/cgi-bin/trac.cgi
116
119 flumotion(1),flumotion-manager(1),flumotion-admin(1)
120Fluendo 2005 July 13 flumotion-worker(1)