Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!rws From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler) Newsgroups: comp.windows.x Subject: Re: Wish list R5 Message-ID: <9007211510.AA00205@expire.lcs.mit.edu> Date: 21 Jul 90 15:10:26 GMT References: Sender: daemon@athena.mit.edu (Mr Background) Organization: The Internet Lines: 18 Today I had a server crash, it dumped the core and prompted for my password again. So far so good. But when my .clients finished another window poped into existance: the xterm of the previous session, running perfectly with the correct history. I'm shure that it's the previous window, because it's pid is inferior to the xserver. What does "inferior to the xserver" mean? If you mean the pid is a smaller number, please prove to me that your kernel didn't wrap around pid allocations, or otherwise somehow generate a lower pid. For example, give me a way to deterministically reproduce the problem. I can't imagine how any xterm implementation I know of would survive a server crash. The only think I can remotely imagine is that an xterm from some previous session was wedged in the kernel, not yet having completely established a connection to the server. If you were using xdm and an MIT server and MIT-MAGIC-COOKIE-1 authorization, the xterm still would have failed to come up (if you aren't using those, it's your fault you have security problems :-).