Date: Fri, 18 Apr 2003 01:45:01 +0700 From: Max Khon <fjoe@iclub.nsu.ru> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: HEADS UP: new NSS Message-ID: <20030418014500.B94094@iclub.nsu.ru> In-Reply-To: <200304171535.h3HFZEFs094589@strings.polstra.com>; from jdp@polstra.com on Thu, Apr 17, 2003 at 08:35:14AM -0700 References: <20030417141133.GA4155@madman.celabo.org> <1050590195.76150.8.camel@owen1492.uf.corelab.com> <20030417144449.GA4530@madman.celabo.org> <200304171535.h3HFZEFs094589@strings.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hi, there! On Thu, Apr 17, 2003 at 08:35:14AM -0700, John Polstra wrote: > > > Out of curiosity, how do the staticly-linked binaries in /bin and /sbin > > > handle this since they can't dlopen anything? Do users handled by > > > dynamically-loaded NSS modules just show up as UIDs with no name in > > > /bin/ls? > > > > Yep. > > The following is a work-around: > > > > cd /usr/src/bin/ls > > make clean > > make NOSHARED=NO depend > > make NOSHARED=NO > > make NOSHARED=NO install > > You might want to look at how libpam handles this situation. In the > static case, all of the known modules are linked into it statically. > Then they are located and registered at runtime by means of a linker > set. statically linking pam_ldap to /bin/ls will be a nightmare :) we need either allow dlopen(3) to be used in statically linked programs or move to dynamically linked /. /fjoe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030418014500.B94094>