Hans,
Did you add the entries to the appropriate PAM configuration files? On
the distributions I am familiar with (Turbolinux and Redhat) those files
are in the /etc/pam.d directory. You need to add the following line to
each of those files that configure services for which you want new jobs
to be created. For example, here is what my /etc/pam.d/login files
looks like on one of my systems:
[watters@paradox watters]$ cat /etc/pam.d/login
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_pwdb.so shadow nullok
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_pwdb.so
password required /lib/security/pam_cracklib.so
password required /lib/security/pam_pwdb.so nullok use_authtok
session required /lib/security/pam_pwdb.so
session optional /lib/security/pam_job.so
session optional /lib/security/pam_console.so
[watters@paradox watters]$
The /lib/security/pam_job.so entry is the one to be added to support job
creation for the login process. This will cause login to create a new
job whenever it is used as the service for entry onto the system. I
suggest using the "optional" parameter until you feel comfortable with
the behavior of job creation. Then you should change it to "required".
I have added this entry to the following files on my system (in
/etc/pam.d directory):
[watters@paradox pam.d]$ fgrep pam_job.so *
ftp:session optional /lib/security/pam_job.so
gdm:session optional /lib/security/pam_job.so
kde:session optional /lib/security/pam_job.so
login:session optional /lib/security/pam_job.so
mcserv:session optional /lib/security/pam_job.so
passwd:session optional /lib/security/pam_job.so
rlogin:session optional /lib/security/pam_job.so
rsh:session optional /lib/security/pam_job.so
su:session optional /lib/security/pam_job.so
xdm:session optional /lib/security/pam_job.so
--
Sam Watters Resource Mgmt Team SGI watters@xxxxxxx
|