Date: Wed, 17 May 2000 23:35:52 -0400 From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: Gary Rafe <grafe@lab12.ie.pitt.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Problem with X after 3.4 -> 4.0 Message-ID: <20000517233552.A62582@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <200005172204.e4HM4Ch09334@lab12.ie.pitt.edu>; from grafe@lab12.ie.pitt.edu on Wed, May 17, 2000 at 06:04:12PM -0400 References: <200005172204.e4HM4Ch09334@lab12.ie.pitt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 17, 2000 at 06:04:12PM -0400, Gary Rafe wrote: > I noticed this behavior, too, of xinit and Xwrapper > last night just after I upgraded from 3.3R/PAO to 4.0R via CDROM > on my Toshiba 4030CDT notebook: > > Authentication failed - cannot start X server > Perhaps you do not have console ownership? > > The server runs just fine when it's made suid. > > Can someone comment on/document the proper PAM configuration > on a 4.0R system for X to run with the correct authorizations ? IIRC, when I looked in the source when I had this problem, X is looking for a pam_console.so module. This does not exist on a FreeBSD install. I think I found some source for pam_console, but it was Linux specific. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000517233552.A62582>