[pulseaudio-tickets] [PulseAudio] #46: autospawn problem

[PulseAudio]

#46: autospawn problem
--------------------+-------------------------------------------------------
 Reporter:  ZlatkO  |       Owner:  lennart
     Type:  defect  |      Status:  new    
 Priority:  normal  |   Milestone:         
Component:  daemon  |    Severity:  minor  
 Keywords:          |  
--------------------+-------------------------------------------------------
 I don't know if this is intentional or not, but {{{autospawn=1}}} doesn't
 work if I specify a default server in either {{{client.conf}}} or on the
 command line (ie. {{{paplay -s unix:/tmp/pulse-zlatko/native
 /some/file.wav}}}).

 What I want to achieve is to have pulseaudio autospawn on demand, and make
 sure that local clients use the socket connection rather than TCP/IP, by
 specifying {{{default-server=unix:/tmp/pulse-zlatko/native}}} in
 {{{client.conf}}}. However, pulseaudio seems to assume that the server is
 already running if I do that, and applications then fail with
 {{{Connection failure: Connection refused}}} rather than ''first''
 autospawning the daemon, and ''then'' connecting via the local socket.

 Autospawning works fine if I don't specify a (default) server, but the
 logfile entries seem to suggest that the clients use TCP/IP rather then
 socket connections in that case. I'd ''really'' like to eliminate the
 TCP/IP overhead if possible, even though I assume it's rather small - is
 there any solution other than dropping {{{autospawn=1}}} completely, and
 running a permanent pulseaudio daemon with {{{default-server=unix:/tmp
 /pulse-zlatko/native}}} instead?

 Thanks in advance!

-- 
Ticket URL: <http://pulseaudio.org/ticket/46>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server