Date: Sun, 5 Oct 2003 13:39:58 -0700 (PDT) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net> To: Joe Lewis <joe@relia.net> Cc: freebsd-questions@freebsd.org Subject: Re: Anyone using Linux-PAM on 5.x? Message-ID: <20031005132836.Y3248@atlas.home> In-Reply-To: <1097.67.2.79.212.1065380548.squirrel@email.relia.net> References: <3F7F29C5.7030606@relia.net> <20031004164554.X3248@atlas.home> <1097.67.2.79.212.1065380548.squirrel@email.relia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 5 Oct 2003, Joe Lewis wrote: > I know of the specification. However, I have a customized version of the > pam-mysql module that I have tried to install. In a previous post to this > list about a week or two ago, I wrote about getting only the following > entrys in the log file (an example of one from today) : > > Oct 5 13:04:15 sharktooth login: in opempam_load_module(): no > pam_mysql.so found > Oct 5 13:04:15 sharktooth login: pam_start(): failed to load module > > Now, it is there in the /usr/lib/ directory, it has the correct > permissions, correct owner, etc. In the /etc/pam.d/login file, I've even > put in absolute paths, and non-aboslute paths. I've copied existing > module entries, changing only the module name (such as pam_unix to > pam_mysql). Looks like dlopen() fails. Is your module linked with any libraries other than libpam and libc? Such as libmysql... :) Unset LD_LIBRARY_PATH and check what "ldd ./pam_mysql.so" says (or read and grok the output of objdump -p). Anything listed as "not found" will result in exactly the error you are seeing, and the problem can be resolved using the normal linker tricks: symlink/copy or ldconfig or build with -R etc... > > Hmmm... odd; the modules all build and work just fine, modulo some > > minor tweaks mostly related to gcc 3.x, even though I have never built > > them on FreeBSD 5 before. Definitely no worse than when porting to > > certain commercial platforms. > > Can you at least point me to some documentation? I don't mind porting the > module. I've copied the pam_unix.c module that comes with the openpam > source code (dogwood release, the one in 5.x), changed references from > pam_unix to pam_mysql, leaving the actual implementations in place so I > make sure that I'm not messing something up, and STILL get the same log > file entries, so it can't be the code in the module. What's the deal? I'm willing to bet on link problems. If I remember correctly one has to rebuild the openpam lib in order to enable debug logging, but it may be worth the effort if nothing else helps. $.02, /Mikko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031005132836.Y3248>