Hi Ivo,

On Tue, Aug 07, 2012 at 10:43:39PM +0200, Ivo De Decker wrote:
> Package: pam
> Version: 1.1.3-7.1
> User: multiarch-de...@lists.alioth.debian.org
> Usertags: multiarch

> When examining pam multiarch issues, I noticed this error (in
> /var/log/auth.log):

> PAM unable to dlopen(pam_smbpass.so): /lib/security/pam_smbpass.so: cannot
> open shared object file: No such file or directory

> The modules are not in /lib/security anymore (but in /lib/<triplet>/security).
> Pam should log the error with the path where the module is supposed to be.

How does PAM know the path where the module is supposed to be?  It's not in
either path - PAM knows this because it's checked both.  And not all pam
module packages in the archive are converted for multiarch.  Why should PAM
use one path over the other in the error message?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slanga...@ubuntu.com                                     vor...@debian.org

Attachment: signature.asc
Description: Digital signature

Reply via email to