"Fossies" - the Fresh Open Source Software Archive
Member "mumble-1.3.2/README.static.linux" (9 Jul 2020, 4230 Bytes) of package /linux/misc/mumble-1.3.2.tar.gz:
As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard
) with prefixed line numbers.
Alternatively you can here view
the uninterpreted source code file.
1 M U M B L E
3 A voicechat utility for gamers
7 #mumble on freenode
10 What is Murmur?
13 Murmur is the server component of Mumble, an open-source voice chat utility.
15 This package is a statically compiled version of Murmur for Linux. It is
16 independent of your distribution's package manager, and is intended to be
17 run as-is, or with minimal set up.
20 Running Murmur
23 In this build of Murmur, the binary is called 'murmur.x86'. To get Murmur
24 up and running, simply execute the following command at your shell:
26 $ ./murmur.x86 -fg -ini murmur.ini
28 This will spawn a foregrounded (Murmur will, by default, run in daemon mode,
29 which means it will launch itself as a background process on your system).
32 The First Run
35 When Murmur runs for the first time, it performs a few special initialization
36 steps, such as setting up its database, as well as generating a certificate
37 for its initial server and a password for the SuperUser user.
39 This password is important for setting up the Murmur server, so make a note
40 of it. It is output by the Murmur server the first time it runs, and will
41 look something like this:
43 <W> HH:MM:DD 1 => Password for 'SuperUser' set to '<YourSuperUserPassword>'
46 Initial User Setup
49 Murmur has the concept of a 'SuperUser', which is the initial administrative user
50 used to configure your server. Typically, this user will only be used for initial
51 setup, and in recovery situations. A regular user, with some administrative privileges
52 is usually set up as a first step. To do this, follow the steps below:
54 1. In your Mumble client, ensure that you have a certificate for your user.
55 (A certificate is generated by Mumble by default, but you can create a new
56 one if you wish -- or use an existing S/MIME email certificate if you wish.)
58 2. Connect to your server with the user that you wish to grant administrative
59 privileges to. (Your username will be stored on the server when you register
60 yourself, so pick something you'd like to keep!)
62 3. Once connected, right click your user name in the server view and choose
63 'Register'. This will register your user to the server (this makes the
64 server remember you as a user -- but you still will not have administrative
67 4. Once registered, you can disconnect from the server. Now it is time to
68 connect using the SuperUser account that the server created for you
69 when you launched it the first time.
71 Simply specify SuperUser as your username, and the password that Murmur
72 gave you as the password.
74 5. After connecting as the SuperUser, right click the 'Root'-channel and
75 choose Edit. In the Edit dialog, click the Groups tab.
77 In the Groups dropdown, choose the admin group.
79 Then, under Members three lists should appear, showing Members, Excluded
80 Members and Inherited Members. We're only interested in Members. Expand
81 the drop down below the member list and find the username of the user
82 you registered in step 3.
84 Click Add to add the user to the admin group.
86 6. Your user is now an administrator.
88 For more advanced setup and usage of Murmur, please visit the Mumble Wiki,
89 at http://mumble.info/. Some pages of interest are available at:
95 Additional Murmur Options
98 The above instructions use a very bare-bones approach to running Murmur.
99 Several other command line options are available. These are listed below:
101 murmur.x86 [-supw <password>] [-ini <inifile>] [-fg] [v]
103 -supw Set new password for the user SuperUser, which is hardcoded to
104 bypass ACLs. Keep this password safe. If you use this option,
105 Murmur will set the password in the database and then exit.
107 -ini Use an ini file other than murmur.ini, use this to run several
108 instances of Murmur from the same directory. Make sure each
109 instance is using a separate database. (Specified in the ini file.)
111 -fg Run in the foreground, logging to standard output.
113 -v More verbose logging.