They way I worked out a similar situation (I am doing an ssh from the box into the box and sometimes from a different box into it) was to setup the PA of the user I ssh as and it IS a user that I would never login directly as to use PA over the network. So as long as someone is logged in then it's PA works. You could have a couple of different configurations sitting around and do some shell trickery and start different configurations depending on the environment.<div> </div><div>Does PA support conditional config files? Maybe it can be all kept in the PA file and just set an environment variable. <div> Fred F <div class="gmail_quote">On Tue, Feb 9, 2010 at 11:59 AM, Markus Rechberger <<a href="mailto:mrechberger@gmail.com">mrechberger@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> On Tue, Feb 9, 2010 at 5:17 PM, Bill Cox <<a href="mailto:waywardgeek@gmail.com">waywardgeek@gmail.com</a>> wrote: > The corking stuff in PA is very cool. I don't think anyone objects to > it. But couldn't we quell all the "PA stinks!" posts by just allowing > some processes/groups/users to have constant access to audio? > > Comparisons to MAC and Windows have been going on for a while, and the > PA guys are basically right that PA is more like Windows and Mac than > the older sound systems. If I'm not mistaken, the real issue is all > the very valid reasons people out in Linux land have for multi-user > simultaneous access to sound. I'd say those guys are generating most > of the negative PA e-mails I read, and not just on this forum. > you cannot compare it with mac, on mac multiuser access works like it worked with alsa and OSS. The only point is that this behavior should be considered to be fixed up again in future. I would not wonder if a remote login in windows as a different permitted user would provide audio support. I do agree that when the user behind the PC is switched that those audio instances should be exclusive. But remote terminals are a different topic and should be handled different. the problem I see with that design is that as soon as the user logs out the PA process might vanish again so you are really stuck with the system daemon if you want to get multiuser support. although another possibility might that other PA daemons connect to the first PA instance and just pass through the first instance might do some user accounting and only shut down when all other PA instances are gone but in that case the system wide mode seems to be more elegant again... Markus _______________________________________________ pulseaudio-discuss mailing list <a href="mailto:pulseaudio-discuss@mail.0pointer.de">pulseaudio-discuss@mail.0pointer.de</a> <a href="https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss" target="_blank">https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss</a> </blockquote></div> </div></div>