Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!convex.UUCP!strike
From: strike@convex.UUCP (Professor Fate)
Newsgroups: comp.windows.x
Subject: xdm question
Message-ID: <8904250225.AA07185@convexs>
Date: 25 Apr 89 02:25:49 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 22


I am having some trouble with xdm. 

I run xdm to serve several different kinds of foreign servers, e.g., Sun's, 
X terminals.  The xdm host is a CONVEX C120.

If I start xdm, and then I start the server or power on the X terminal, xdm 
detects that the server is now accepting connections and displays the login 
window.

However, if my Sun crashes, or if I power off the X terminal, and the xdm login
window was being displayed, xdm will not send a new login window when the 
server is available again (after reboot or power on). The problem is that xdm
does not detect that the server has gone away (and come back again.) The
xdm child process that is waiting for input in the login window is stuck 
in select() deep in the bowels of Xt.

There is a lot of code in xdm - some if it seems unused. Has this problem been
solved already. I seem to remember some discussion about xdm about three months
ago or so.  Is there a solution to this problem?

M