How to do proper PAM modul configuration? (was: Testing: Warning messages from su within cron)

[Stephan Seitz]

On Mon, Feb 03, 2014 at 11:11:24PM +1100, Scott Ferguson wrote:

On 03/02/14 22:55, Stephan Seitz wrote:

I’m using Testing. For some time I’m getting warning messages from
scripts started via cron, e.g.:
/etc/cron.daily/popularity-contest:
su: No module specific data is present
/etc/cron.daily/spamassassin:
su: No module specific data is present
su: No module specific data is present
su: No module specific data is present

I couldn't find anything in my notes, but I did turn up this (in a
search engine). Is it related/helpful?
http://debian.2.n7.nabble.com/Bug-736642-schroot-PAM-error-No-module-specific-data-is-present-td3161399.html

Thank you, this is the solution.






Shade and sweet water!

        Stephan

--
| Stephan Seitz          E-Mail: s...@fsing.rootsland.net |
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |

I commented the pam_ssh.so line in /etc/pam.d/common-session, and the warnings are gone. But now the ssh-agent autoconfiguration is lost. I’m wondering what the right solution is? Don’t use pam-auth-update? I’ll change the subject and hope that other people with PAM experience will answer.

smime.p7s
Description: S/MIME cryptographic signature