Path: utzoo!attcan!uunet!lll-winken!ames!apple!bloom-beacon!kadmon.UUCP!jason
From: jason@kadmon.UUCP (Jason Venner)
Newsgroups: comp.windows.x
Subject: Re: X protocol question (I solved my problem).
Message-ID: <202.611513045@kadmon>
Date: 18 May 89 16:44:05 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 30


It turned out that for some reason I was not getting SIGIO's on the
sockets, and I was using that to determine whether to read off of the
X socket.

The fact that this would cause the X server to crash is another
problem...

[Senario was:
	 program listening at 6001 and X1
	 and with a io channel to another machine with a real X server
	 at X0/6000
	 on other machine, program listening on the io channel, and
	 when it recieves a new connection connecting to Real X and X0

	 I had done the usual for SIGIO's (fcntl setown, flags = FASYNC,
	 handler for SIGIO's....)
	 but the process which open'd the socket to the Real X server
	 never got one, and then the X server would die often a few
	 minutes after I had killed all of the processes.]

 So, I changed the code not to need SIGIO's
	 
	Jason
Jason Venner
Jason@spar.stanford.edu
jason@mtxinu.com
jason@violet.berkeley.edu
jason@ucbviolet.bitnet
{...,ucbvax}!mtxinu!jason