Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: rxvt 2.7.10-6: bash Control-C exits all backgrounded children  rxvt processes as well as foreground process/command
Date: Mon, 27 Jun 2005 15:28:43 -0400
Message-ID: <F71C0DC6B4FD3648815AAA7F969E3529015302E6@sr002-2kexc.ateb.com>
From: "Reid Thompson" <Reid DOT Thompson AT ateb DOT com>
To: <cygwinquery AT joethefish DOT com>, <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j5RJStmW011481

jxshea AT regence DOT com wrote:
> I have some wrappers to invoke a telnet or an ssh within an
> rxvt window so that I can label it with the host I'm
> connecting to.  I love rxvt because it has real vt emulation,
> and also gives me X-like middle mouse cut and paste
> operations that I'm used to from my Sun environment, but all
> without the overhead of running X.  However, a really
> annoying and quite hazardous artifact of rxvt in cygwin is
> that it will grab the control-Cs sent from the parent bash
> session and close down.  Unfortunately, pings, by default are
> unlimited in iteration and so must be killed when you're done
> with it and also, I'm in the habit of using control-C to quit
> a command line in progress to get back to a prompt.
> 
> Unless I remember to to start a new bash window to do
> anything where I might send a Control-C, I end up clobbering
> the 20 odd telnet/ssh sessions I have up, some of which could
> contain important processes that are difficult to recover from being
> terminated. 
> 
> Any advice on
> 
> 1)  Whether this is an issue with bash or rxvt or both?
> 2)  Any workarounds i.e.- application flags for rxvt or bash
> that I can code in to avoid this behavior.
> 
> Thanks in advance.
> 
> Jackson Shea
> cygwinquery AT joethefish DOT com
> 
> ==================================
> ==      wrapper scripts         ==
> ==================================
> 
> telnet script:
> 
> #!/usr/bin/bash
> echo "telnet $1" > /tmp/cmdfile.$$
> chmod a+x /tmp/cmdfile.$$
> rxvt -sl 2000 -fn 9x18 -fg yellow -bg black -title $1 -e
> /tmp/cmdfile.$$ & sleep 5 rm /tmp/cmdfile.$$
> 
> ssh script:
> 
> #!/usr/bin/bash
> echo "telnet $1" > /tmp/cmdfile.$$
> chmod a+x /tmp/cmdfile.$$
> rxvt -sl 2000 -fn 9x18 -fg yellow -bg black -title $1 -e
> /tmp/cmdfile.$$ & sleep 5 rm /tmp/cmdfile.$$
> 

I do not see this effect for either of the above wrappers...


reid

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/