SOLVED: XFree86 lockfile?
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 this did the trick, after i started it, it gave the report that it couldn't find the computername. I checked the DNS entry's and they where all correct. After that i checked the /etc/hosts and saw that there was an error there. (the computername was listed multiple times with diverent IP's). After correcting this, xdm gave my Xserver a beautifull login prompt. :-) Thnx for helping me out guys! Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: SOLVED: XFree86 lockfile?
On Friday, 3 January 2003 at 11:11:13 +0100, Marcel Stangenberger wrote: 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 this did the trick, after i started it, it gave the report that it couldn't find the computername. I checked the DNS entry's and they where all correct. After that i checked the /etc/hosts and saw that there was an error there. (the computername was listed multiple times with diverent IP's). After correcting this, xdm gave my Xserver a beautifull login prompt. :-) Glad to hear that we've solved the problem. But looking back, consider the approach. Reinstalling seldom helps. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
In article info.freebsd.questions/[EMAIL PROTECTED] you wrote: I was working in my X-client lastnight (i use Exceed from my workstation to connect to the X-Client on my FreeBSD server) when i lost my dhcp lease due to a faulty config. Because of this my X session crashed. Now my Xclient refuses to give me a logon screen when i start Exceed. I'm guessing it has a file somewhere saying that i'm still logged in or something. But i can't seem to find this file (or any other reason for this beheavure). Can anyone tell me what is going on and how i can fix this? Sometimes the X server or other X components are still running. In similar circumstances, I use ps axw | grep X and kill any X components that I see. I've tried restarting xdm (killall -HUP xdm) but that didn't help. I've also restarted the entire machine, but that didn't help either. I've just tried to connect using another computer, but that didn't work either. So i'm now thinking of reinstalling XFree86 Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, Jan 02, 2003 at 12:34:09PM +0100, Marcel Stangenberger wrote: In article info.freebsd.questions/[EMAIL PROTECTED] you wrote: I was working in my X-client lastnight (i use Exceed from my workstation to connect to the X-Client on my FreeBSD server) when i lost my dhcp lease due to a faulty config. Because of this my X session crashed. Now my Xclient refuses to give me a logon screen when i start Exceed. I'm guessing it has a file somewhere saying that i'm still logged in or something. But i can't seem to find this file (or any other reason for this beheavure). Can anyone tell me what is going on and how i can fix this? Sometimes the X server or other X components are still running. In similar circumstances, I use ps axw | grep X and kill any X components that I see. I've tried restarting xdm (killall -HUP xdm) but that didn't help. I've also restarted the entire machine, but that didn't help either. I've just tried to connect using another computer, but that didn't work either. So i'm now thinking of reinstalling XFree86 Marcel Ugh, hopefully it won't come to that :-( You might have been onto something with your comment about lock files -- XFree86 creates various hidden files in /tmp, for instance I have: .ICE-unix/ .X0-lock .X110unix/ You might try deleting all of those (if you have them) and restarting xdm again. I'm not entirely sure it'll help, but it's worth a try. HTH, Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines [EMAIL PROTECTED] | 0xAA775B8B | -- Anon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
Ugh, hopefully it won't come to that :-( You might have been onto something with your comment about lock files -- XFree86 creates various hidden files in /tmp, for instance I have: .ICE-unix/ .X0-lock .X110unix/ You might try deleting all of those (if you have them) and restarting xdm again. I'm not entirely sure it'll help, but it's worth a try. I tried doing that, but it didn't work either. I just uninstalled XFree86 and recompiled and installed it from the ports (thank god for fast computers), but it still isn't working. i don't see what is wrong, a friend of mine just said the only solution is to reinstall the entire machine, but i don't really consider that to be an option. Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, 2 Jan 2003, Marcel Stangenberger wrote: Date: Thu, 2 Jan 2003 15:29:58 +0100 (CET) From: Marcel Stangenberger [EMAIL PROTECTED] To: Brent J. Ermlick [EMAIL PROTECTED] Cc: Scott Mitchell [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: XFree86 lockfile? On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 02:52:22PM +0100, Marcel Stangenberger wrote: . . . i don't see what is wrong, a friend of mine just said the only solution is to reinstall the entire machine, but i don't really consider that to be an option. That doesn't make sense. What errors do you see in /var/log/XFree86.0.log? -- XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.7-RELEASE-p2 i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 1 10:02:54 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Looks to me like XFree86 can't find its configuration file, which by default is in /etc/X11/XF86Config. This file needs to be generated by a configuration program. You can either do this in /stand/sysinstall or by running 'xf86config' manually, which is my preferred method. Re-installing the box is certainly not necessary. I mean, this isn't Windows ;) # John Bleichert # http://vonbek.dhs.org/latest.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 03:29:58PM +0100, Marcel Stangenberger wrote: . . . (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 1 10:02:54 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Ah -- I think this is important. You need to reconfigure X. XFree86 -configure I just did so and reconfigured X, i placed the file in /etc/ en restarted xdm. It now says the following in XFree86.0.log -- XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.7-RELEASE-p2 i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Thu Jan 2 16:02:37 2003 (++) Using config file: /root/XF86Config.new (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Sp eedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (**) ModulePath set to /usr/X11R6/lib/modules (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on freebsd (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1039,0635 card , rev 11 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:02:0: chip 1039,0008 card , rev 00 class 06,01,00 hdr 80 (II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev d0 class 01,01,80 hdr 80 (II) PCI: 00:09:0: chip 5333,8a01 card 5333,8a01 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:0d:0: chip 10b7,9004 card 10b7,9004 rev 04 class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 1000,0001 card 1000,1000 rev 23 class 01,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x02 (VGA_EN is cleared) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xd7e0 - 0xd7ef (0x10) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xd7c0 - 0xd7cf (0x10) MX[B] (II) Bus -1: bridge is at (0:2:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(0:9:0) S3 ViRGE/DX or /GX rev 1, Mem @ 0xdc00/26, BIOS @ 0xdbff00 00/16 (II) Addressable bus resource ranges are [0] -1 0x - 0x (0x0) MX[B] [1] -1 0x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 0xffe0 - 0x (0x20) MX[B](B) [1] -1 0x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 0x000f - 0x000f (0x1) MX[B] [3] -1 0x000c - 0x000e (0x3) MX[B]
Re: XFree86 lockfile?
On Thu, Jan 02, 2003 at 04:18:48PM +0100, Marcel Stangenberger wrote: . . . so i assume X is working on the server now (i don't have a monitor on the server) but i'm not getting a login prompt on my Exceed :( the xdm.log is empty so there are no errors reported by xdm. xdm is started properly from /etc/ttys i also rechecked the xdm config files (Xaccess, Xsession, xdm-config and others) and they are still correct. Whoops. I thought that the X server and the client were on the same machine. I apologize. The X server is the machine with the monitor. If there are two different machines, then it looks as if the problem is with the Exceed. That is where you need to look for locks and protection issues. Make sure that you have run the xhost command (or the equivalent on the Exceed) so that the Exceed allows clients running on the FreeBSD machine (such as xdm and xterm) to display on the screen of the Exceed. -- Brent J. ErmlickVeritas liberabit uos [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, Jan 02, 2003 at 04:18:48PM +0100, Marcel Stangenberger wrote: . . . so i assume X is working on the server now (i don't have a monitor on the server) but i'm not getting a login prompt on my Exceed :( the xdm.log is empty so there are no errors reported by xdm. xdm is started properly from /etc/ttys i also rechecked the xdm config files (Xaccess, Xsession, xdm-config and others) and they are still correct. Whoops. I thought that the X server and the client were on the same machine. I apologize. The X server is the machine with the monitor. If there are two different machines, then it looks as if the problem is with the Exceed. That is where you need to look for locks and protection issues. Make sure that you have run the xhost command (or the equivalent on the Exceed) so that the Exceed allows clients running on the FreeBSD machine (such as xdm and xterm) to display on the screen of the Exceed. I've tried reinstalling exceed but that didn't help. I disabled the xhosts so that it will allow any client to display but that doesn't help either. I've also tried using X-Win32 on this system (and on my laptop) but that doesn't work either. It's very odd. Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, Jan 02, 2003 at 05:28:44PM +0100, Marcel Stangenberger wrote: . . . I've tried reinstalling exceed but that didn't help. I disabled the xhosts so that it will allow any client to display but that doesn't help either. I've also tried using X-Win32 on this system (and on my laptop) but that doesn't work either. It's very odd. XFree86-4.+ has more security than the older versions of X. Instead of disabling xhosts, try making sure that the FreeBSD server is explicitly allowed to access the X server on your other machine. -- Brent J. ErmlickVeritas liberabit uos [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 05:28:44PM +0100, Marcel Stangenberger wrote: . . . I've tried reinstalling exceed but that didn't help. I disabled the xhosts so that it will allow any client to display but that doesn't help either. I've also tried using X-Win32 on this system (and on my laptop) but that doesn't work either. It's very odd. XFree86-4.+ has more security than the older versions of X. Instead of disabling xhosts, try making sure that the FreeBSD server is explicitly allowed to access the X server on your other machine. i just tried that on both Exceed and X-Win32 but both still don't give a login prompt Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 05:28:44PM +0100, Marcel Stangenberger wrote: . . . I've tried reinstalling exceed but that didn't help. I disabled the xhosts so that it will allow any client to display but that doesn't help either. I've also tried using X-Win32 on this system (and on my laptop) but that doesn't work either. It's very odd. XFree86-4.+ has more security than the older versions of X. Instead of disabling xhosts, try making sure that the FreeBSD server is explicitly allowed to access the X server on your other machine. I tried multiple security settings but it didn't help. I just removed the XFree86-4 installation from my system and installed the /usr/ports/x11/XFree86 one instead. This one also does not provide a login prompt after installation and configuration of xdm. I recon that it must be a X / FreeBSD issue because it used to work on both my laptop and my workstation and now it doesn't work on both. If it is a windows issue caused by the crash that happend in my Exceed when my workstation lost its DHCP lease then it should still work on my laptop. Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
On Thursday, 2 January 2003 at 15:29:58 +0100, Marcel Stangenberger wrote: On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 02:52:22PM +0100, Marcel Stangenberger wrote: . . . i don't see what is wrong, a friend of mine just said the only solution is to reinstall the entire machine, but i don't really consider that to be an option. That doesn't make sense. What errors do you see in /var/log/XFree86.0.log? (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 1 10:02:54 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() This, of course, was the result of reinstalling X. That's not what you should do. On Thursday, 2 January 2003 at 9:23:57 -0500, John Bleichert wrote: On Thu, 2 Jan 2003, Marcel Stangenberger wrote: On Thu, 2 Jan 2003 15:29:58 +0100 (CET), Marcel Stangenberger wrote: On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 02:52:22PM +0100, Marcel Stangenberger wrote: . . . i don't see what is wrong, a friend of mine just said the only solution is to reinstall the entire machine, but i don't really consider that to be an option. That doesn't make sense. What errors do you see in /var/log/XFree86.0.log? -- XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 1 10:02:54 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Looks to me like XFree86 can't find its configuration file, which by default is in /etc/X11/XF86Config. This file needs to be generated by a configuration program. Specifically, for XFree86 version 4, run xf86cfg or X -configure. The former puts the configuration file in /usr/X11R6/lib/X11/XF86Config. Be sure that you don't have an old config file in one of these places: /etc/XF86Config /etc/X11/XF86Config /usr/X11R6/etc/XF86Config /usr/X11R6/lib/X11/XF86Config.hostname /usr/X11R6/lib/X11/XF86Config X -configure puts it in ~/XF86confg.new. You have to move it to your favourite place manually. You can either do this in /stand/sysinstall or by running 'xf86config' manually, which is my preferred method. Re-installing the box is certainly not necessary. I mean, this isn't Windows ;) I don't recommend using xf86config any more. It's much more painful than the others, and it doesn't appear to be maintained any more. On Thursday, 2 January 2003 at 16:18:48 +0100, Marcel Stangenberger wrote: On Thu, 2 Jan 2003, Brent J. Ermlick wrote: On Thu, Jan 02, 2003 at 03:29:58PM +0100, Marcel Stangenberger wrote: Ah -- I think this is important. You need to reconfigure X. XFree86 -configure I just did so and reconfigured X, i placed the file in /etc/ en restarted xdm. It now says the following in XFree86.0.log -- XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) (II) Keyboard Keyboard0 handled by legacy driver (II) XINPUT: Adding extended input device Mouse0 (type: MOUSE) (**) Option BaudRate 1200 -- so i assume X is working on the server now (i don't have a monitor on the server) but i'm not getting a login prompt on my Exceed :( Why do you have a server without a monitor? That's completely nonproductive. the xdm.log is empty so there are no errors reported by xdm. xdm is started properly from /etc/ttys i also rechecked the xdm config files (Xaccess, Xsession, xdm-config and others) and they are still correct. I think you're confusing the purpose of an X server. It's for displaying things on a monitor. If you don't have a monitor, you don't need an X server. On Thursday, 2 January 2003 at 22:55:33 +0100, Marcel Stangenberger wrote: On Thu, 2 Jan 2003, Brent J. Ermlick wrote: XFree86-4.+ has more security than the older versions of X. Instead of disabling xhosts, try making sure that the FreeBSD server is explicitly allowed to access the X server on your other machine. I tried multiple security settings but it didn't help. I just removed the XFree86-4 installation from my system and installed the /usr/ports/x11/XFree86 one instead. 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. I may be misunderstanding; there's a lot of confusion here. Can you clarify: - Which machines are running X? - On which machine(e) did you reinstall X? - Which X client are you talking about? - What is exceed? - Can you run X normally on your local machine? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe
Re: XFree86 lockfile?
On Fri, Jan 03, 2003 at 10:19:36AM +1030, Greg 'groggy' Lehey 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 an X server for Win32 machines. I assume he's been using it as an X terminal onto the FreeBSD machine. I should have noticed that earlier, but the X server/client distinction always confuses people, especially when you're dealing with X terminals :-( Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines [EMAIL PROTECTED] | 0xAA775B8B | -- Anon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
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. I may be misunderstanding; there's a lot of confusion here. Can you clarify: - Which machines are running X? My FreeBSD server (eldar) - On which machine(e) did you reinstall X? on eldar - 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. 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: XFree86 lockfile?
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 [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
XFree86 lockfile?
Hi all, Happy newyear to everybody. I was working in my X-client lastnight (i use Exceed from my workstation to connect to the X-Client on my FreeBSD server) when i lost my dhcp lease due to a faulty config. Because of this my X session crashed. Now my Xclient refuses to give me a logon screen when i start Exceed. I'm guessing it has a file somewhere saying that i'm still logged in or something. But i can't seem to find this file (or any other reason for this beheavure). Can anyone tell me what is going on and how i can fix this? Greetings, Marcel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
