Where or how does SuSE KDE set certain permissions correctly ?
Hi there, if you use KDE from SuSE it correctly sets certain permissions like /dev/dsp if you logon. Now I installed KDE 3.1 on my own, if I logon as user "test" the permissions for /dev/dsp still belong to "malte_gell". If I use SuSE's KDE it always sets the permissions correctly for the user who logs on. Which way does SuSE use to set those permissions ? I'd like to use this for my self compile KDE 3.1. Thanx Malte
Hi Malte! On my SuSE 7.3 it's configured through /etc/logindevperm Greets, Daniel Am Freitag, 31. Januar 2003 21:02 schrieb Malte Gell:
Hi there,
if you use KDE from SuSE it correctly sets certain permissions like /dev/dsp if you logon.
Now I installed KDE 3.1 on my own, if I logon as user "test" the permissions for /dev/dsp still belong to "malte_gell". If I use SuSE's KDE it always sets the permissions correctly for the user who logs on.
Which way does SuSE use to set those permissions ? I'd like to use this for my self compile KDE 3.1.
Thanx Malte
Am Freitag, 31. Januar 2003 21:09 schrieb Daniel Eckl:
Hi Malte!
On my SuSE 7.3 it's configured through /etc/logindevperm
I'm also using SuSE 7.3 and checked /etc/logindevperm which contains all the necessary things, including /dev/dsp* The question remains, why the *ownership* does not change to the user who logs on, so if I logon as "test" the ownership of /dev/dsp does not change to "test". When using KDE from SuSE the ownership changes correctly at logon... So this may be a general KDE issue when I compiled 3.1 ? PAM is installed and should have been detected, I didn't give any special options with ./configure. Strange... So there's no SuSE script which changes the ownership when logging on ? Regards, Malte
hmmm, I think it's made through PAM, too. I have a line in /etc/pam.d/xdm that reads: session required pam_devperm.so I think, that your kdm is not recognized as pam-service xdm. you can try to copy /etc/pam.d/xdm to /etc/pam.d/kdm (just a guess)... Or you can check in your kdmrc, if kdm uses /var/lock/xdm.pid as pidfile, perhaps this is most decisive for pam... Greets, Daniel Am Freitag, 31. Januar 2003 21:35 schrieb Malte Gell:
Am Freitag, 31. Januar 2003 21:09 schrieb Daniel Eckl:
Hi Malte!
On my SuSE 7.3 it's configured through /etc/logindevperm
I'm also using SuSE 7.3 and checked /etc/logindevperm which contains all the necessary things, including /dev/dsp*
The question remains, why the *ownership* does not change to the user who logs on, so if I logon as "test" the ownership of /dev/dsp does not change to "test". When using KDE from SuSE the ownership changes correctly at logon...
So this may be a general KDE issue when I compiled 3.1 ? PAM is installed and should have been detected, I didn't give any special options with ./configure. Strange...
So there's no SuSE script which changes the ownership when logging on ?
Regards, Malte
Am Freitag, 31. Januar 2003 21:09 schrieb Daniel Eckl:
Hi Malte!
On my SuSE 7.3 it's configured through /etc/logindevperm
Hhmm... could please do grep devperm /etc/pam.d/kde* grep devperm /etc/pam.d/xdm* I guess if I have a missing entry session required pam_devperm.so in /etc/pam.d/kde so I'm curious what the grep commands from above will tell if you could do this on your machine. Thanx ! Malte
participants (2)
-
Daniel Eckl -
malte_gell＠t-online.de