Hello,

I've been trying to get xlock to unlock when using nis on RHL 4.2 systems. 
It does not seem to like it when the authentication is through an NIS
server, but will unlock when the user is listed properly in /etc/passwd
and /etc/shadow. 

Apr 15 11:40:58 eupa PAM_pwdb[7377]: 1 authentication failure; (uid=1045) -> ted for 
xlock service
Apr 15 11:42:56 eupa PAM_pwdb[7388]: 1 authentication failure; (uid=1045) -> ted for 
xlock service
Apr 15 11:45:23 eupa PAM_pwdb[7398]: 1 authentication failure; (uid=1045)-> ted for 
xlock service

I suspect it may have something to do with PAM.  Where, /etc/pam.d/xlock
looks like:

#%PAM-1.0
auth       required     /lib/security/pam_pwdb.so shadow nullok

vs.  /etc/pam.d/login which looks like:

#%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 shadow nullok use_authtok
session    required     /lib/security/pam_pwdb.so

I tried making /etc/pam.d/xlock look like the entries in login, but it
didn't work.  So I put xlock back to its original state.

Does anyone have any ideas on this matter?

Thanks,

-ted

------------------------------------------------------
Ted Smith                         [EMAIL PROTECTED]
Physics Computer Services / UCSB  tel.805.893.8366
Santa Barbara, CA  93106          fax.805.893.3307
------------------------------------------------------



-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to