On Fri, Mar 07, 2003 at 09:19:04AM -0500, Bob Paige wrote:What about running X locally and starting the window manager remotely? I _think_ the advantages would be:
Another variable, just in case it will shed any light: I'm using a USB ethernet adapter (Linksys USB100M; very small). I've heard in the past of problems with USB ethernet adapters disconnecting and causing problems, but even when I was running the locally installed image it never froze like this.
My luck with USB NICs has been pretty bad as well. Any chance of going to a more reliable connection?
Keep in mind that with XDMCP, the display is being managed by a remote machine. If you lose contact with that machine (like, say, because of a flaky NIC), would you not expect the terminal to appear to have locked up? It may be running fine itself, but if it can't send input to the XDMCP server or get display updates back...
1. less sensitive to NIC hiccups; assuming my NIC is being flaky, I never noticed before when running locally-hosted applications, so I would think that the connection would be re-established before a TCP timeout (wouldn't it?)
2. window manager would present a list of apps installed on the server (not the client)
Of course, the biggest disadvantage is starting the whole thing up because it would require a manual step to go to connect to the server and start the window manager, but I might be able to script that. Also, since it is running at home (behind a NAT box) I'm not so concerned about being hacked.
-- Bobman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
