From owner-freebsd-questions Thu Jan 2 22:49:18 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB4DB37B401 for ; Thu, 2 Jan 2003 22:49:15 -0800 (PST) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 237E343EA9 for ; Thu, 2 Jan 2003 22:49:13 -0800 (PST) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 8CC8C5194E; Fri, 3 Jan 2003 17:19:10 +1030 (CST) Date: Fri, 3 Jan 2003 17:19:10 +1030 From: Greg 'groggy' Lehey To: Marcel Stangenberger Cc: John Bleichert , "Brent J. Ermlick" , Scott Mitchell , questions@FreeBSD.ORG Subject: Re: XFree86 lockfile? Message-ID: <20030103064910.GE43679@wantadilla.lemis.com> References: <20030102152110.I199@eldar.hayholt.org> <20030102111401.GA65231@bermls.oau.org> <20030102123215.I207@eldar.hayholt.org> <20030102131257.GA4945@fishballoon.dyndns.org> <20030102145019.G199@eldar.hayholt.org> <20030102141916.GA59713@bermls.oau.org> <20030102152110.I199@eldar.hayholt.org> <20030102234936.GF57152@wantadilla.lemis.com> <20030103061318.E195@eldar.hayholt.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030103061318.E195@eldar.hayholt.org> User-Agent: Mutt/1.4i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, 3 January 2003 at 6:21:51 +0100, Marcel Stangenberger wrote: >> This is not going to work. Don't reinstall without a good reason. >> What's more, it's pretty clear that you're looking in the wrong >> place. I've looked at your original message and you say you're using >> the server to connect to your local client. That's wrong. It looks >> as if exceed is a client (I've never heard of it), and it's not >> connecting to your local server (display). Reinstalling X remotely is >> obviously not going to do anything. > > Exceed is the server, XFree86 is running the client. XFree86 is > running on my FreeBSD box, Exceed is running on my windows box. In this case, reinstalling the X server on the FreeBSD box isn't going to help. >> I may be misunderstanding; there's a lot of confusion here. Can you >> clarify: >> >> - Which machines are running X? > > My FreeBSD server (eldar) Well, it has clients. Normally when we say "running X", we mean the server. >> - On which machine(e) did you reinstall X? > > on eldar Hmm, and then you tried to start the server on a machine without a monitor? I don't suppose it does any harm, but it's not necessary. >> - Which X client are you talking about? > > the eldar is the X client > >> - What is exceed? > > Exceed is a X server to be used in windows > >> - Can you run X normally on your local machine? > > it used to work until i lost my dhcp lease and since then it doesn't work > anymore. Nothing at all? > The reason i'm looking at the freebsd machine, is because it doesn't > work on both my workstation (which i was using at the time of the > dhcp incident) and on my laptop which i wasn't using at that > time. Since the dhcp incident the Xserver never gives a login > prompt, but it does pop up the chooser. I'm not sure what a chooser is, but the X server doesn't have a login prompt. There are things like xdm which do. I'm afraid I don't know enough about Microsoft to give you any further information, but since you say that it happened after the DHCP lease expires, you should check your configuration files on the Microsoft machine to see if they are making any assumptions about IP addresses. You could also try manually starting the client on eldar, pointing it at the (running) X server on your Microsoft box. Something like: xterm -display microsoft:0 (substituting the system name for "microsoft", of course). This also assumes that your server is running as display 0, which is normal but not essential. If that doesn't work, I'd suggest you use a FreeBSD machine with a server and see if that can access eldar. If that doesn't work either, we can investigate what's going on there. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message