[comp.windows.x] xhost bug on Sun

dce@mips.COM (David Elliott) (11/30/88)

I haven't seen this problem discussed before, and have no idea yet as
to whether it persists in X11R3.

One of the users here, using all the same server and client software
the rest of us are using, had a problem in which starting more than a
few clients would result in new clients getting server protocol
errors.  It was as though he had hit a limit on the number of clients
you can have running, since killing a client allowed starting another
client.  It turned out that the user had his X startup file set up with
a set of lines like:

	xhost {host1}
	xhost {host2}
	...
	xhost {hostn}

When he changed this to "xhost +", the problem went away.  Additionally,
users executing "xhost {host1} {host2} ... {hostn}" don't seem to
run into this problem.

I verified this problem by changing my startup script to run 24 xhost
commands, and was able to start only a single client before getting
the server protocol error messages.

I noticed nothing in the xhost manual page about it being incorrect
to run multiple xhost commands.

-- 
David Elliott		dce@mips.com  or  {ames,prls,pyramid,decwrl}!mips!dce
"Did you see his eyes?  Did you see his crazy eyes?" -- Iggy (who else?)

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (12/07/88)

    I verified this problem by changing my startup script to run 24 xhost
    commands, and was able to start only a single client before getting
    the server protocol error messages.

I cannot reproduce this in R3.