Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!samsung!usc!ucsd!nosc!helios.ee.lbl.gov!pasteur!ucbvax!NISC.SRI.COM!cwilson
From: cwilson@NISC.SRI.COM (Chan Wilson)
Newsgroups: comp.windows.x
Subject: bug?
Message-ID: <9639@fs2.NISC.SRI.COM>
Date: 7 Nov 89 22:52:33 GMT
References: <9638@fs2.NISC.SRI.COM>
Reply-To: cwilson@beanie.UUCP (Chan Wilson)
Organization: Network Info Systems Ctr., SRI Intl., Menlo Park, CA.
Lines: 15

While mucking around with X windows, I telneted over to one of the 
SparcStations and did a 'xinit -display mymachine:0'  This didn't work. 
Moreever, the display on the sparcstation was locked (unbeknownst to me) so 
I couldn't check the display out.  When the user of the workstation came in 
the following morning, she was quite distressed to see the display unlock, 
have my default x setup appear, and then slowly, messily, crash and burn. 

Is this a bug?  I mean, shouldn't xinit check to see if the display it is
going to be using is locked. (or is this even possible?)


--Chan Wilson
	     `and now for something completely different.'
	Flamingo coloured penguins and banana coloured grapes.
              cwilson@nisc.sri.com or cwilson@nic.ddn.mil