Can't a system daemon use some authentication method (like a remote pulseaudio daemon authenticating remote requests) to authenticate and authorize local audio usage requests? That would simplify permissions problems, when PA starts and even allow multiple access for multiple users (should it be desired). Does consolekit expose a remote service that would allow processes to authenticate processes connecting to it using their PID? On Sat, 2008-02-23 at 10:38 +0000, Colin Guthrie wrote: > JaM wrote: > > Do you have pulseaudio starting on a per user basis or as a service? > > What are the benefits/disadvantages of each? > > Per user. > > It's the recommended way as it allows things like user switching to work > as expected (e.g. when I login as a second user, the first user's sound > is effectively muted). This is all handled thanks to consolekit. > > Also with a system daemon you have added user management overheads > (users have to be in a certain group to access the daemon etc.) > > Col > > _______________________________________________ > pulseaudio-discuss mailing list > pulseaudio-discuss at mail.0pointer.de > https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss >
