trouble with pam

When we originally implemented perdition v1.17 on RHEL4 several years 
ago we had a customized the /etc/pam.d/perdition file to use the 
pam_access.so module so we could lock out accounts for 
administrative/maintenance purposes. This worked well for many years.

Within the last year we upgraded to RHEL5 and perdition 1.19rc4 and then 
rc5. It would appear that since this update perdition no longer seems to 
pay any sort of attention to the contents of the pam file and will 
always assume success. Nothing seems to be logged either unlike before. 
Although we are now compiling perdition to be located in /usr/perdition 
with it's conf files in /etc/perdition I don't see how that would affect 
pam operations, at least I would think it shouldn't. ldd on perdition 
does show pam libraries being linked. Any ideas?

thanks,
David

-- 
David Severance
Enterprise Unix Services
Office of Information Technology
(949) 824-7552
[email protected]

______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users