From owner-freebsd-questions Mon Mar 16 14:41:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16639 for freebsd-questions-outgoing; Mon, 16 Mar 1998 14:41:08 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from tera.com (tera.tera.com [207.108.223.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16551 for ; Mon, 16 Mar 1998 14:40:58 -0800 (PST) (envelope-from kline@tao.thought.org) Received: (from uucp@localhost) by tera.com (8.7.5/8.7.3) with UUCP id OAA11952; Mon, 16 Mar 1998 14:39:45 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.5/8.7.3) id OAA27228; Mon, 16 Mar 1998 14:38:59 -0800 (PST) From: Gary Kline Message-Id: <199803162238.OAA27228@tao.thought.org> Subject: Re: XDM In-Reply-To: from Spike Gronim at "Mar 16, 98 04:14:40 pm" To: spork@cncn.com Date: Mon, 16 Mar 1998 14:38:58 -0800 (PST) Cc: freebsd-questions@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Spike Gronim: > Hello. > > I would like to configure XDM. I have "The complete FreeBSD", and > it said to put a line like > "ttyvX "/usr/X11R6/bin/xdm -nodaemon" xtrerm on secure" > in my /etc/ttys file. > > It presented me with login: and password: and a console log. I > typed my name/ password, and the screen blanked and then came back to the > same login screen. When I typed an incorrect login, it said incorrect > login, so it is recognizing me. I found the server output (included) in > /usr/X11R6/lib/X11/xdm/xdm-errors. I don't really understand how to > configure xdm, and if anybody has any pointers it would be appreciated. > > When I couldn't log in via XDM, I cut it out of the ttys file. I kill > -HUPed 1, and it was still running. So, I killed it and it's accompanying > console reading proccess. I was at the console (ttyv0) at the time. It > hung my terminal at the least and the system at worst, as it would just > beep when I hit a key. I rebooted the computer, it fscked root (after > warning about improper reboot) and then halted on the fscking of /usr. I > dropped to singleuser by hitting ^C, and manually fscked /, /usr and /var. > I hit ^D, and the system proceeded to boot. Why did xdm do this to my > system when I tried to kill it? > > Much of what you describe happened to me when I was installing X Window Window Managers on my new box. The things that you must have in your /home account are an ~/.xsession file that had the xterms, and other x tools that you want; and the name on the WM. For example xterm -fn 9x15bold & ctwm & and so forth. Additionally, your ~/.xsession file must be mode 0755; i.e. executable. Try this and get back to the list.... gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message