Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Start of my Fedora 6 build/setup

  • David McKeon
    David McKeon

    Install and build mumble on Fedora 6

    Installing mumble, download the packages:
    Install Yum Packages:
    yum install qt4.i386 qt4-devel.i386 qt4-sqlite.i386 qt4-mysql.i386 qt4-x11.i386
    ln -fs /usr/lib/libsqlite3.so.0.8.6 /usr/lib/libsqlite.so.0
    yum install qt-MySQL.i386 qt4-sqlite.i386

    Building Mumble on Fedora 6

    To build mumble, type
    qmake-qt4 mumble.pro
    lrelease mumble.pro
    make -f Makefile.mumble release

    Building Murmur on Fedora

    To build murmur, type
    qmake-qt4 murmur.pro
    lrelease murmur.pro
    make -f Makefile.murmur release

    Which will help a bit for those people trying to get it running on fedora. There is also a need to put the latest speex binary/development out, which fedora non Dev version, aka Fedora 6 will not get this file by default.
    wget http://downloads.us.xiph.org/releases/speex/speex-1.0.5-1.i386.rpm
    wget http://downloads.us.xiph.org/releases/speex/speex-devel-1.0.5-1.i386.rpm
    rpm -U speex-1.0.5-1.i386.rpm
    rpm -U speex-devel-1.0.5-1.i386.rpm
    You might have to run -ihv here or -U with –nodeps –force options depending on what you have installed.

    How to change SuperUser Password after setup, this is the administrative user. Cut and paste this script to change_pw.ksh in the same location you are going to home your murmur database.

    ################ cut here


    dmckeon Nov 2, 2006

    Free as in beer script to set the Superuser account in a new

    murmur install or reinstall.

    http://murmur.sourceforge.net for murmur

    echo " Switch Murmur SuperUser Password"
    echo " You need to run this in the same location as the murmer.sqlite file!"
    echo ""
    echo "1) To change SuperUser Password"
    echo ""
    echo "q) to quit"
    echo ""
    printf '==> '
    #### END MENU ####
    read answer
    case ${answer} in
    printf 'Type Password ==> '
    stty -echo
    read PW
    stty echo
    printf '\nRe-type Password ==> '
    stty -echo
    read PW2
    stty echo
    echo " "
    if [ ${PW} -ne ${PW2} ]
    echo "Passwords to not match retry script. No Changes Exiting.."

                        murmur -supw $PW
                        #assume the user wants to quit
                        echo ""
                        echo "Exiting menu.."
                        echo "This is the default clause. we are not sure why or"
                        echo "what someone would be typing, but perhaps you should read the menu."
                        echo ""
                        exit 1
    ########## End Cut

    Or run the command: Be aware though that this will put your password in your .bash_history file, or shell history if not bash, which is a very bad thing, the above script will not.

    murmur -supw <password>

    Change password by hand in murmur.sqlite
    sqlite3 murmur.sqlite
    <Inside sqlite>
    UPDATE players SET pw = 'newpassword' WHERE name = 'playername';
    BE AWARE the above set of commands places the password in the .sqlite3 history file in your home directory. This is not a good thing.

    DOWNLOAD the sqlite browser
    wget http://prdownloads.sourceforge.net/sqlitebrowser/sqlitebrowser-1.3-i386.tar.gz?download
    tar -zxf sqlitebrowser-1.3-i386.tar.gz
    you can then run sqlitebrowser and open the murmur.sqlite database – careful in there dont tinker if you do not understand it.

    Install gkrellm2 on Fedora 6
    yum -y install gkrellm.i386 gkrellm-freq.i386 gkrellm-hddtemp.i386 gkrellm-themes.noarch gkrellm-devel.i386

    To Install fchart for gkrellm2:
    Install http://www.cs.hmc.edu/~geoff/gkrellm-fchart.html for gkrellm
    wget http://www.cs.hmc.edu/~geoff/tars/gkrellm-fchart-1.0.1.tgz
    tar -zxf gkrellm-fchart-1.0.1.tgz
    cd gkrellm-fchart-1.0.1
    su -c "cp ./fchart.o /usr/lib/gkrellm2/plugins/"

    Configure fchart:
    Install pinger test verify everything works.
    Label: hdfsplnstby1
    file to chart: /tmp/pinger.txt
    cmd: /home/dmckeon/scripts/pingtimer -i 4 -b /tmp/pinger hdfsplnstby1
    warning cmd: /usr/bin/zenity --info --text 'Ping Test lantency check warning!'
    alert cmd: /usr/bin/zenity --info --text 'Ping Test lantency ALERT'

    To look at the number of connections you have without being logged into the server:
    Get this setup in gkrellm, make sure you have the scripts in the right spot or change paths.
    setup gkrellm config, select internet, put in label murmur, port0 64738

    vi /etc/services put in “mumble 64738/tcp # mumble”

    Things yet to do:
    Install the perl dbi for sqlite3
    Write a query that pulls out the number of sessions and how long they have been on.
    Write an output file that can be used by gkrellm fchart to chart usage.
    Write a way to store this information for trending and graphics, also we might want to grab CPU load versus number of users, also grab memory.

    QUOTE about bandwidth I'm working on :
    Bandwidith usage from FAQ:
    What sort of bandwidth will I need for the server?
    Worst case scenario: Number of users × Number of talking users × 60 kbit/s. With less aggressive quality settings, it's ~20 kbit/s, and the bare minimum is 12kbit/s. Note that Mumble is geared towards social gaming; its quality enables people to talk naturally to each other instead of just barking short commands, so the amount of "users talking at the same time" can be somewhat higher than expected.
    This means that a server with 20 players and 2 players talking at once requires 0.8-2.4 Mbit/s, depending on quality settings. In the server's .ini file, you can specify the maximum allowed bitrate for users as well as the maximum number of clients to allow.

    I'm looking to improve this as I get time, feel free to send me feedback mckeond2003 (at) yahoo (dt) com