[pulseaudio-discuss] Sharing logged in users instance over TCP better than systemwide daemon?

Graeme Pietersz graeme.pietersz at gmail.com
Sat Dec 10 02:21:28 PST 2011

I want a shared PC on a home LAN to be able to play a stream uninterrupted through one sound card (connected to a decent amp and speakers in the sitting room) while allowing other users to login and use another sound card if they wish.

I was planning to use a system-wide daemon, but after reading the warnings about it, I wondered if this was a better solution:

Following the suggestion in this thread:


Have an auto logged in user that starts pulseaudio with:

load-module module-native-protocol-tcp

in its ~/.pulse/default.pa

all other users have:

default-server =

in  ~/.pulse/client.conf

That way any local user or anyone on the LAN can play a stream though this machine.

Is this better than a system-wide daemon in any way? Is it better supported?

Obviously, allowing any user access is not a security issue as that is what I want (it would be good to restrict network access to the microphone though, but its not essential).

Latency an issue as it will mostly be used for music and broadcast streams. Having an automatically logged in user is also not a problem as I want one shared user anyway.


Graeme Pietersz

More information about the pulseaudio-discuss mailing list