Re: DE features dependent on Systemd
- To: debian-devel@lists.debian.org
- Subject: Re: DE features dependent on Systemd
- From: Andreas Bombe <aeb@debian.org>
- Date: Mon, 1 Dec 2014 02:10:09 +0100
- Message-id: <[🔎] 20141201011009.GA5355@amos.fritz.box>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <87r3wkmykq.fsf@violet.siamics.net>
- References: <201411262329.26670.envite@rolamasao.org> <87zjbd33to.fsf@hope.eyrie.org> <1417047554.17080.2.camel@kagura.malsain.org> <87a93aotd9.fsf@violet.siamics.net> <1417339417.25136.4.camel@debian.org> <87ppc5ngm5.fsf_-_@violet.siamics.net> <m3ppc4ucje.fsf@neo.luffy.cx> <873890onsa.fsf@violet.siamics.net> <1417355600.5458.7.camel@debian.org> <87r3wkmykq.fsf@violet.siamics.net>
On Sun, Nov 30, 2014 at 04:40:21PM +0000, Ivan Shmakov wrote:
> >>>>> Josselin Mouette <joss@debian.org> writes:
> > * Other users only have access to audio devices through ACLs when
> > physically logged on.
>
> Unless I be mistaken, ACLs are only applied at the time of
> open(2). What about the processes (if any) which opened an
> audio device back when it was possible, but are still running at
> the time the user logs out?
That is how Linux works, yes. revoke() syscalls have been occasionally
proposed for at least 15 years but as far as I know no implementation
has yet been accepted in the Linux kernel.
I don't know if logind can do or does anything beyond that.
Andreas
Reply to: