Comment 12 for bug 1274821

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Well, it's stock CentOS 5 vs stock CentOS 6, they are both the same, and the save version of our software works on 6 but not on 5, with the same configuration. Both bug reported and Nil just did it all (PAM configuration steps) by the manual.

If any special configuration is needed for CentOS 5, our manual for PAM should say this explicitly. It was already proved that one has to add:

account required pam_permit.so

on CentOS 5 to make PAM work. Proved and double checked that this is not needed on CentOS 6 or other Linux. So, we clearly have a problem to fix in http://www.percona.com/doc/percona-pam-for-mysql/manual.html#configuring-pam-for-mysql that says nothing about pam_permit.so or CentOS 5 specifically. Current state must be properly documented, even if eventually PAM is going to be fixed to make this extra module not needed.

I am not sure how to prove there is internal failure to fix (strace, something else). Specific instructions would be really helpful.