Message: previous - next
Month: February 2014

Re: [trinity-devel] Bug 1902 - pam.d and preprocessor checks surrounding consolekit may be part of issue

From: "David C. Rankin" <drankinatty@...>
Date: Tue, 25 Feb 2014 13:53:13 -0600
On 02/25/2014 12:03 AM, François Andriot wrote:
> Le 25/02/2014 05:43, David C. Rankin a écrit :
>> On 02/24/2014 10:34 PM, David C. Rankin wrote:
>>> showing that session tracking can with
>> Grrr... autotext, should be:
>> showing that session tracking can work in TDE...
> Here are the PAM files I'm using on Mageia 4.
> This is simply a copy/paste from what KDE4 uses on the same distribution.
> I've done some investigation on this issue and I'll write my findings later (not
> enough time right now).
> Francois

Thank you Francios,

  On Arch the only pam file was /etc/pam.d/trinity:


auth       required
auth       requisite
auth       include      system-local-login
account    include      system-local-login
session    include      system-local-login

  I updated it to test the Arch kde4 /apm file:

auth            include         system-login
account         include         system-login
password        include         system-login
session         include         system-login

  However, that made no difference (system-local-login is just an alias of
system-login). There was no 'kdescreensaver' in the Arch TDE install, so I
created a 'tdescreensaver' pam file:


auth            required

  Again, it made no difference. I have poked around the mkpamserv executable and
think I can patch it for arch to generate the tdescreensaver file on tdebase
install, but I'm still not clear on how/where in the code to insure the name
'tdescreensaver' will be recognized as a pam file by the system. (the
inter-workings of pam are a learning experience as well). I'll test with your
config and report back. If you get the process tracking figured out, let me
know. Thanks.

David C. Rankin, J.D.,P.E.