On Wed, 2014-12-17 at 17:47 +0200, Imran Zaman wrote: > > > I'm not very familiar with the tty concept, and I don't know what the > > PAM_TTY variable is supposed to mean exactly... My assumptions: the VT > > number corresponds to the function key number when I switch terminals > > with Ctrl-Alt-F<N>. The tty number is related to the VT number, but they > > are not exactly the same thing. Maybe ttys are only assigned to text > > logins, while the VT can also be graphical? That theory is supported by > > the fact that pam_sm_open_session() in src/login/pam_systemd.c sets the > > tty variable to NULL in case of X11, cron and ssh logins before passing > > it to logind. If the tty number is relevant only in the context of text > > logins, and you're dealing with graphical logins, maybe the right thing > > would be to unset PAM_TTY or set it to an empty string? > > > > Just tested PAM_TTY="" and Active=yes can be seen below. But the real > problem is that /dev/snd/* is still following normal ACL as you can for > the access rights for /dev/snd/* below, which is what we are wondering > that which component is actually setting the ACL when PAM_TTY=tty1?
I'm sure it's logind. Based on the file name, I'd guess src/login/logind-acl.c would be a good place to start looking. -- Tanu _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
