From owner-freebsd-ports@FreeBSD.ORG Sat Jul 25 17:05:59 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7A28106566B; Sat, 25 Jul 2009 17:05:59 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out10.libero.it (cp-out10.libero.it [212.52.84.110]) by mx1.freebsd.org (Postfix) with ESMTP id A9DCF8FC12; Sat, 25 Jul 2009 17:05:59 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (151.51.38.102) by cp-out10.libero.it (8.5.107) id 4A5DDB5B010DC0F3; Sat, 25 Jul 2009 18:54:23 +0200 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.3/8.14.2) with ESMTP id n6PGsMJR063088; Sat, 25 Jul 2009 18:54:23 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <4A6B38BE.2050405@netfence.it> Date: Sat, 25 Jul 2009 18:54:22 +0200 From: Andrea Venturoli User-Agent: Thunderbird 2.0.0.22 (X11/20090624) MIME-Version: 1.0 To: freebsd-ports@freebsd.org, marcus@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: netatalk 2.0.4 breaks PAM? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2009 17:06:00 -0000 Hello. I'm using afpd on a 6.3/i386 and I make it authenticate to pam_smb. Everything was fine with 2.0.3. As soon as I upgraded to 2.0.4, I started getting: Jul 13 09:28:38 xxxxx afpd[89271]: dhx login: yyyyyyy Jul 13 09:28:38 xxxxx afpd[89271]: in openpam_load_module(): no /usr/local/lib/pam_smb_auth.so found Jul 13 09:28:38 xxxxx afpd[89271]: uams_dhx_pam.c :PAM: PAM_Error: system error Jul 13 09:28:38 xxxxx afpd[89271]: 0.18KB read, 0.12KB written I swear /usr/local/lib/pam_smb_auth.so is there and working, since many other packages are using it the same way. Since this is a production environment, I had to downgrade to 2.0.3 as fast as possible; everything worked fine again since then. Not sure if this is a FreeBSD port's specific problem, but I thought I'd start here. bye & Thanks av.