Date: Mon, 27 Jun 2005 15:43:08 +0200 From: Florent Thoumie <flz@FreeBSD.org> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, freebsd-current@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: OpenPAM Figwort broke PAM modules from ports Message-ID: <42C0026C.3040000@FreeBSD.org> In-Reply-To: <20050627130449.GQ1283@obiwan.tataz.chchile.org> References: <20050626211011.GH1283@obiwan.tataz.chchile.org> <86d5q8113a.fsf@xps.des.no> <20050627130449.GQ1283@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremie Le Hen wrote: > Hi Dag-Erling, > > >>>This prevents PAM modules installed in /usr/local/lib from being >>>dlopen(3)'d. I'm not sure whether FreeBSD really wants this new >>>``feature'' or not, but actually I think this needs a note in >>>src/UPDATING to be issued, explaining that PAM modules installed from >>>ports need to be specified with their full path now. >> >>They always did. > > > With all respect I owe you you, the last upgrade of my -CURRENT box > constrained me to use the following patch to make pam_alreadyloggedin.so > work again : FWIW, I always needed to put full pathname for pam_ldap to use it. -- Florent Thoumie flz@xbsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42C0026C.3040000>