On Mon, Feb 10, 2003 at 01:38:13AM +0100, Dag-Erling Smorgrav wrote: > Olivier Dony <[EMAIL PROTECTED]> writes: > > Actually I had patched pam_mysql (on FreeBSD 4.x when pam_mysql was still > > working, to be able to use blowfish correctly with FreeBSD's crypt(), but my > > problem is really to get an OpenPAM module to work, I even tried to simply > > rename the pam_permit one, but have the same problem: openpam_load_module > > won't find/open it now matter what... > > In /usr/src/contrib/openpam/lib/openpam_dynamic.c, change at least the > first two instances of PAM_LOG_DEBUG to PAM_LOG_ERROR, then rebuild > libpam (cd /usr/src/lib/libpam && make && make install) and try again.
Ah, that's great, I will do that immediately, it sure will help anyway. Too bad I didn't see your second reply earlier, the openpam debug was part of the problem. > OpenPAM will now log messages in /var/log/messages showing why it > fails to load your module. My guess is that your module requires a > library which you forgot to add to LDADD. Exactly, hehe, thank you ! :-) I definetly should have read your second mail, but I was busy playing with those funny PAM modules... Explanation in my previous reply with [SOLVED]. > BTW, the PAM module makefiles in the tree aren't standalone: they rely > on variables set in Makefile.inc one and two levels up. Amongst other > things, they add a version number to the dynamic module, and prevent > the static version from being installed. Ok, that's a good thing to know, I read most of those Makefiles but didn't pay much attention ;-) Thanks so much for your help again! Olivier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
