Remove the *-pc symlinks in the /etc/pam.d directory and create real files for common-account, common-auth, common-session and common-password
pam-config will still run but will only operate on the -pc files and your system will ignore the changes Tom On 04/04/14 01:18 PM, Wendy Lin wrote: > This question is offtopic but related to my other problems with pam_krb5.so: > How can I tell Suse's yast to NOT run pam-config each time a software > update is done? It destroys my custom /etc/pam.d/common-auth settings. > > Wendy > ________________________________________________ > Kerberos mailing list [email protected] > https://mailman.mit.edu/mailman/listinfo/kerberos ________________________________________________ Kerberos mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/kerberos
