From owner-freebsd-current Mon Dec 27 21:36: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 7F61D152F8 for ; Mon, 27 Dec 1999 21:35:58 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id NAA50991; Tue, 28 Dec 1999 13:38:57 +0800 (CST) (envelope-from clive) Date: Tue, 28 Dec 1999 13:38:57 +0800 From: Clive Lin To: "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Problem with PAM-AUTH for XFree86? Message-ID: <19991228133857.A50959@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote: > Hello, > > I just got my box up and running Current 12-27. ATA works great for both drives now. However, I compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many password prompts. I can only assume that the PAM module used for athentication by XFree86 is broken. Is the owner aware of this? > > I recompiled without PAM support and everything works as expected. > Hi! I dunno if this is tooo tricky, but I added a single line to solved the same question as yours. the xserver line... X clive@cartier ~> tail -5 /etc/pam.conf # tricky tricky forgive me xserver auth sufficient pam_permit.so no_use # If we don't match anything else, default to using getpwnam(). other auth required pam_unix.so try_first_pass other account required pam_unix.so try_first_pass X clive@cartier ~> -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message