On Tue, 09.02.10 09:43, Markus Rechberger (mrechberger at gmail.com) wrote: > > Indeed. PA is principally meant to be run per-user. Each user logged in > > will have their own PA process running and each will monitor a system > > service called "ConsoleKit" which tracks which user is active. We adhere > > to whatever ConsoleKit tells us with regards to which user is currently > > "active" (see ck-list-sessions) and only the active user has access to > > the sound hardware. > > > > Think about how switching users works (on Linux and on Windows/OSX). > > Only the user whose desktop is currently presented will be allowed to > > use sound, the other user's sound is "corked" until they become active > > again. > > > Bad example as usual, on OSX everyone (who's permitted to use the > audio unit) can just log in and use the audio unit. Do we need to have this pointless discussion every second months? Last time I checked OSX audio of the sessions that are not in the foreground is paused, and only one session has access to the sound cards at a time. Exactly like on PA, or on Windows. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net http://0pointer.net/lennart/ GnuPG 0x1A015CC4
