> Date: Wed, 8 Nov 2017 09:13:34 -0500 > From: Mark Gregory <[email protected]> > To: [email protected] > Subject: Re: [blfs-support] ConsoleKit2-1.0.2 cannot find PAM module > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > On 11/06/2017 03:00 PM, [email protected] > wrote: >> Send blfs-support mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.linuxfromscratch.org/listinfo/blfs-support >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of blfs-support digest..." >> >> >> Today's Topics: >> >> 1. ConsoleKit2-1.0.2 cannot find PAM module (Mark Gregory) >> 2. Re: ConsoleKit2-1.0.2 cannot find PAM module (Ken Moffat) >> 3. Tips for speeding up X startup? (Paul Rogers) >> 4. Re: Tips for speeding up X startup? (Michael D.) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 5 Nov 2017 15:05:24 -0500 >> From: Mark Gregory <[email protected]> >> To: [email protected] >> Subject: [blfs-support] ConsoleKit2-1.0.2 cannot find PAM module >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset=utf-8 >> >> I am trying to install ConsoleKit2-1.0.2 per the BLFS Version 8.1 book >> with the Required (dbus-glib-0.108 and Xorg Libraries) and Recommended >> (Linux-PAM-1.3.0, Polkit-0.113+git_2919920+js38, and pm-utils-1.4.1) >> packages previously installed. >> >> I have tried it a couple times, reinstalling Polkit and Linux-PAM and >> Shadow, but keep getting a message during ./configure that it can't find >> the PAM module. >> >> Here are the last few lines of the configure script before it quits: >> checking zlib.h presence... yes >> checking for zlib.h... yes >> checking for pam_getenv in -lpam... no >> checking security/pam_modutil.h usability... yes >> checking security/pam_modutil.h presence... yes >> checking for security/pam_modutil.h... yes >> checking security/pam_ext.h usability... yes >> checking security/pam_ext.h presence... yes >> checking for security/pam_ext.h... yes >> checking for pam_syslog in -lpam... no >> >> The two lines ending in "no" appear to be the problem. What do I need >> to look at to diagnose / fix this? >> >> Thanks, >> >>> Hi Mark, > >>> looking at my own logs I agree that the two 'no' items are the >>> problem. When we install Linux-PAM, after 'make install' we run >>> chmod and then we move some libraries from /usr/lib to /lib, and >>> finally we make symlinks to them from /usr/lib. >>> >>> I guess some or all of your symlinks are broken : try running 'file' >>> on them to see if that reports breakage. >>> >>> If the symlinks are indeed broken, please review what you did in the >>> last install of Linux-PAM. The instructions in the book should >>> work. And to fix that : if you can login with PAM then what is in >>> /lib should be fine, so just recreate the symlinks from /usr/lib for >>> each of libpam*.so. >>> >>> ĸen >>> -- >>> Truth, in front of her huge walk-in wardrobe, selected black leather >>> boots with stiletto heels for such a barefaced truth. >>> - Unseen Academicals > > Ken, > > Thank you for the reply. I tried running 'file' but don't know enough > about it to interpret what I was seeing. While researching 'file' I > ran across 'find', which seemed to turn up something that to me appears > might be important. Below is the command line, and results: > > mark [ /usr/lib ]$ find -L ./ -mindepth 15 | grep find: > find: './libpam_misc.so/libpamc.so.0': Too many levels fo symbolic links > find: './libpam_misc.so/libpam.so.0': Too many levels fo symbolic links > find: './libpam_misc.so/libpam.so.0.84.2': Too many levels fo symbolic links > find: './libpam_misc.so/libpamc.so.0.82.1': Too many levels fo symbolic > links > find: './libpam_misc.so/libpamc.so': Too many levels fo symbolic links > find: './libpam_misc.so/libpam.so': Too many levels fo symbolic links > find: './libpamc.so/libpamc.so.0': Too many levels fo symbolic links > find: './libpamc.so/libpam.so.0': Too many levels fo symbolic links > find: './libpamc.so/libpam.so.0.84.2': Too many levels fo symbolic links > find: './libpamc.so/libpamc.so.0.82.1': Too many levels fo symbolic links > find: './libpamc.so/libpamc.so': Too many levels fo symbolic links > find: './libpamc.so/libpam.so': Too many levels fo symbolic links > find: './libpam.so/libpamc.so.0': Too many levels fo symbolic links > find: './libpam.so/libpam.so.0': Too many levels fo symbolic links > find: './libpam.so/libpam.so.0.84.2': Too many levels fo symbolic links > find: './libpam.so/libpamc.so.0.82.1': Too many levels fo symbolic links > find: './libpam.so/libpamc.so': Too many levels fo symbolic links > find: './libpam.so/libpam.so': Too many levels fo symbolic links > > I did a "sudo make uninstall" in the Linux-PAM source directory, which > removed the /usr/lib "libpam" files, but I am uncertain about what to do > with the "libpam" files in /lib. Can I safely remove them using "rm > -rf" without breaking something? My thinking is that I should remove > them and then reinstall Linux-PAM, followed by reinstalling Shadow. > > Am I on the right track? I have learned a lot in this trek through LFS > and into BLFS, so would like to continue. > > Regards, >
Ken, Well, it got worse before it got better! At one point I could not even login at all, so I reinstalled Cracklib, Linux-PAM and Shadow from the host system using chroot. I got it to where I could login, but "su" would not work. I rechecked the Shadow configuration instructions and fixed the /etc/pam.d/login, -/passwd, -/su and -/chage to be exactly as shown on the Shadow configuration instructions, as well as confirming the commented out items in the /etc/login.defs file. Those actions restored the ability to use "su". Somewhere along the way I noticed "Libcap-2.25 with PAM", the description of which contains this line, " if Linux-PAM support is desired, the PAM module must be built (after installation of Linux-PAM)." The reference to the PAM module rang a bell from the original error message while trying to install ConsoleKit2. So, I installed Libcap-2.25 (again, it was in LFS originally), then went on to install ConsoleKit2-1.0.2, with no problems at all. Whew! ConsoleKit2-1.0.2 does not list Libcap-2.25 with PAM as a requirement,nor does Linux-PAM-1.3.0. It seems it should be stated on ConsoleKit2, or possibly Linux-PAM. Thank you for your help and patience. I really appreciate your wisdom. Regards, -- *Mark / AB9ZA* (574) 312-8097 /[email protected]/ -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
