From owner-freebsd-current Mon Feb 11 18:51:56 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id EA1F837B67C for ; Mon, 11 Feb 2002 18:19:27 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 8514023208 for ; Mon, 11 Feb 2002 21:18:19 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 86E8F9F411; Mon, 11 Feb 2002 21:12:52 -0500 (EST) Date: Mon, 11 Feb 2002 20:15:48 -0500 From: Munish Chopra To: freebsd-current@FreeBSD.ORG Subject: Re: PAM Error Message-Id: <20020212021252.86E8F9F411@okeeffe.bestweb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Feb 11, 2002 at 12:04:53PM +0000, markm@FreeBSD.ORG wrote: > > Yesterday I tried to use SWAT for the first time since the PAM configs were > > moved from /etc/pam.conf and I'm getting the following error: > > > > Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open > > /etc/pam.conf > > > > What do I need to do to fix this? > > Recompile the app. I'm guessing it is linked statically, so is not > picking up the latest libpam. > Though that sounds logical to me too, I've had the same errors pop up using a self-compiled 'cups'. I haven't had time to try to chase what's going on. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message