Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mit-eddie!uw-beaver!Teknowledge.COM!unix!ace!ric
From: ric@ace.sri.com (Richard Steinberger)
Newsgroups: comp.windows.x
Subject: Need help debugging CAN'T OPEN DISPLAY msg
Message-ID: <19965@unix.SRI.COM>
Date: 14 Jan 91 22:12:15 GMT
Sender: news@unix.SRI.COM
Reply-To: ric@ace.sri.com (Richard Steinberger)
Organization: SRI International
Lines: 21

I have been using a few Tektronix XP27 X terminals lately.  It is
not uncommon to see a message like, "Cannot open display", even though
I am certain the DISPLAY variable and other syntax and parameters 
are properly set.  For example, the command line:

	rsh myhost xeyes -display myxterm:0.0

will sometimes produce the previously-mentioned message.  At other times,
it will work properly.

While I suspect that this situation results from one or more errors in
the Tektronix server code, I'd like some way to figure out what's really
going on.  Can anyone suggest a strategy to help track this down.  Are
there any contributed X clients that might be run, perhaps from another
terminal or workstation, that can monitor and interpret network messages?
If not, could a network analyzer be useful?  Thanks to all who reply.

regards,

	ric steinberger
	ric@ace.sri.com