[Petter Reinholdtsen] > On second thought, I believe the proper way to configure pam is to > only use pam-devperm for the services providing ttys, and to _not_ > list it in /etc/pam.d/current-session but in /etc/pam.d/login, > /etc/pam.d/gdm, etc. Then at will not try to use the module and > this work properly.
I just got this confirmed by the author (Thorsten Kukuk): To your problem: pam_devperm cannot be put in the common section for all services, you can only put it in config files for special service, which allow a local login to the user (login, kdm, gdm). It does not makes sense to put it in a common section, it will break the applications of the local logged in user. He also mentioned that SUSE dropped pam-devperm two years ago in favor of pam_resmgr. JFYI. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
