I was unable to build the whole Mumble system on CentOS but it's available for Fedora Development. I just wanted the server part on my headless server, and a static build is available from the Mumble project on Sourceforge. So I grabbed the Mumble SRPM from Fedora Development, the static build from Sourceforge, and stripped the spec file down to the minimum needed to just install the static-build server. You'll find the result here: <http://sewingwitch.com/ken/Stuff/murmur-1.2.3-11.kp.src.rpm> If you're paranoid (a good admin should be), just unpack to use the spec file and grab the sources from Fedora Development and Sourceforge and overwrite those included in the SRPM before building.
I found a bug in the RPM: /etc/murmur needs to be owned by mumble-server.mumble-server so that it can write to its sqlite DB.
On 13 March 2011 09:03, Kenneth Porter <shiva at sewingwitch.com> wrote:> I found a bug in the RPM: /etc/murmur needs to be owned by > mumble-server.mumble-server so that it can write to its sqlite DB.There is a great write up in the section "tips and tricks" on the mumble website for installing it on CentOS google knows about it it involves using the static build from sourceforge and extracting the conf and init files from the mandriva rpm then adding the necessary group and user works a treat and "free-er" than teamspeak 3 mike
On 15 March 2011 19:07, Kenneth Porter <shiva at sewingwitch.com> wrote:> > BTW, I found that the initscript included in the Fedora RPM launches the > server as root instead of mumble-server (unprivileged user) and murmur must > drop privs once started. This causes the log file and sqlite DB to be > created owned by root, which causes problems later. The fix is to use the > --user option in the initscript. I need to cut another SRPM to address that. >I suppose that if you are using the default non-privileged port then there is no reason to start as root then drop to mumble-server user. I don't see this behaviour in the mandriva rpm files that i cut out and used. Next stop is getting SELinux to play nicely with it. It is also just another bit of software that i have to track manually though would be much happier to have it in the RPM database as my "check for updates" bookmarked tab group is getting longer and more painful to use. mike