This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Multiple XWin.exe programs loading and no xterm


I wasn'y reffering to your situation specifically.  Even when the script is not
executed twice, two Xwin.exe processes launch.  That is what I described in the
first post of this thread.  As I learned, adding the -kb flag makes the second
Xwin.exe die shortly after the initial launch, but my question is why two are
loading in the first place.

--- "Armbrust, Daniel C." <Armbrust.Daniel@mayo.edu> wrote:
> Because I execute the entire script twice, since the first execution doesn't
> bring up any xterms.
> 
> Still not sure what is causing it to take so long to launch the xwin.exe.
> 
> Can I set the timeout values on the xterm's with a flag?
> 
> Dan 
> 
> 
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-owner@cygwin.com] On
> Behalf Of Scott Cegielski
> Sent: Thursday, March 31, 2005 10:38 AM
> To: cygwin-xfree@cygwin.com
> Subject: RE: Multiple XWin.exe programs loading and no xterm
> 
> I'm just trying to understand this even though it works for me now.  Why are
> two X servers launching in the first place?
> 
> --- Alexander Gottwald <alexander.gottwald@s1999.tu-chemnitz.de> wrote:
> > On Wed, 30 Mar 2005, Armbrust, Daniel C. wrote:
> > 
> > > The -kb command helped with one of my machines that was having
> intermittent
> > difficulties in launching.
> > > 
> > > 
> > > 
> > > On another machine, however, I always have to execute the following
> script
> > twice before I get any Xwin windows:
> > > 
> > > run XWin -multiwindow -clipboard -silent-dup-error -kb
> > > run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
> > /usr/bin/bash -l
> > > run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y
> > username@some.server
> > > 
> > > 
> > > The first time that I run it - Xwin.exe and two xterm.exe's appear in the
> > process manager - then both xterm's disappear.  Eventually the X finally
> > appears in the lower right corner.
> > 
> > This means XWin is taking very long to startup. Maybe because of a virus
> > scanner?
> > The xterms will timeout after no connection to the xserver could be
> > established.
> > The second xserver will notice the first one and will silently exit but now
> > the
> > xterms can connect to the first xserver.
> > 
> > Adding a sleep after run XWin might help by postponing the xterm startup.
> > 
> > bye
> > 	ago
> > -- 
> >  Alexander.Gottwald@s1999.tu-chemnitz.de 
> >  http://www.gotti.org           ICQ: 126018723
> > 
> 
> 
> Scott Cegielski
> scegielski@yahoo.com
> 
> 
> 
> 
> 		
> __________________________________ 
> Do you Yahoo!? 
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/ 
> 


Scott Cegielski
scegielski@yahoo.com




		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]