Difference between revisions of "Pogo"

Revision as of 22:40, 22 January 2013 (view source) Dosman (Talk | contribs) (Created page with "Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible. == Services Pogo provides == * I...")		Revision as of 22:43, 22 January 2013 (view source) Dosman (Talk | contribs) Newer edit →
Line 46:		Line 46:
	Then set it up to start at boot with this:		Then set it up to start at boot with this:
	<pre>chkconfig --add pulseaudio; chkconfig --level 345 pulseaudio on</pre>		<pre>chkconfig --add pulseaudio; chkconfig --level 345 pulseaudio on</pre>
		+
		+	Now festival and other apps can generate audio output regardless if a user is logged into X.

---

Revision as of 22:43, 22 January 2013

Pogo is the name of the system we keep running for services in the space. Generally we try to keep it in a running state as much as possible.

Services Pogo provides

• Internal webserver/fileserver
• External webserver via dynamic dns
• Shell accounts
• RFID access management (RFID operates independently)
• Gateway between RFID system and IRC via doorbot
• Audio and Text annunciation to people within the space
• LDAP (still experimental)

Notes on pulseaudio setup

Previously only a user logged in through X could get audio output on pogo. This is necessary for fun audio stuff like letting the RFID system greet members when they badge into the space.

This is how to get pulseaudio working on pogo so anyone logged in can launch sound from the command line. Note that this is not normally how pulseaudio is supposed to run, in fact the pulseaudio folks explicitly state this is bad and not supported, it's only allowed for strange setups like what we actually need for our use of it on pogo.

Found part of the fix from this link:

• http://wiki.laptop.org/go/PulseAudio

*** PULSEAUDIO: Unable to connect: Access denied

aplay: main:545: audio open error: Connection refused This happens because pulseaudio requires authentication before accepting connections to prevent random people from playing audio on your computer. Pulseaudio places a cookie in the home directories of the user running the server. Copy the cookie of the machine you want to send the audio data to, to the home directory of the sender machine. (Alternatively, you may add auth-anonymous=1 to the end of the load-module module-native-protocol-tcp line to disable authentication). You are ready to play networked audio using pulseaudio.

First verify console kit is installed, there are other ways to use pulseaudio but this is what was working with pulseaudio as of today:

rpm -qa | grep -i consolekit
ConsoleKit-libs-0.4.5-1.fc15.i686
ConsoleKit-0.4.5-1.fc15.i686
ConsoleKit-x11-0.4.5-1.fc15.i686

First fix from the default install: change this line in /etc/pulse/system.pa to this:

#load-module module-native-protocol-unix
load-module module-native-protocol-unix auth-anonymous=1

Also uncomment this line and change to "yes" in /etc/pulse/daemon.pa:

daemonize = yes

At this point pulseaudio can be started and won't die - should accept audio from any user, and probably over the network as well...

/usr/bin/pulseaudio -D --system --disallow-module-loading --disallow-exit

I threw together an init file here: /etc/init.d/pulseaudio Then set it up to start at boot with this:

chkconfig --add pulseaudio; chkconfig --level 345 pulseaudio on

Now festival and other apps can generate audio output regardless if a user is logged into X.