I have been running 3.x and 4.0-CURRENT for some time, but have never bothered using PAM. Yesterday, after a build of 4.0-CURRENT of that day, I decided to try enabling PAM by copying /usr/src/pam.conf to /etc.
My problem is that login fails, due to undefined symbols in the PAM modules: May 28 20:57:32 wopr login: unable to dlopen(/usr/lib/pam_skey.so) May 28 20:57:32 wopr /kernel: pid 12921 (login), uid 0: exited on signal 11 (core dumped) May 28 20:57:32 wopr login: [dlerror: /usr/lib/libskey.so.2: Undefined symbol "sys_siglist"] May 28 20:57:32 wopr login: adding faulty module: /usr/lib/pam_skey.so May 28 20:57:32 wopr login: unable to dlopen(/usr/lib/pam_unix.so) May 28 20:57:32 wopr login: [dlerror: /usr/lib/pam_unix.so: Undefined symbol "ctime"] May 28 20:57:32 wopr login: adding faulty module: /usr/lib/pam_unix.so I tried the following: I added "-lc" to the LDADD line in pam_unix's Makefile. It then apparently resolved the ctime symbol, but then bombed trying to resolve "environ" in libc: May 28 21:04:27 wopr login: unable to dlopen(/usr/lib/pam_unix.so) May 28 21:04:27 wopr login: [dlerror: /usr/lib/libc.so.3: Undefined symbol "environ"] May 28 21:04:27 wopr login: adding faulty module: /usr/lib/pam_unix.so Any ideas? Matt -- Matthew Hunt <m...@astro.caltech.edu> * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
