X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 16 Sep 2007 11:24:38 -0700 From: Gary Johnson To: cygwin AT cygwin DOT com Subject: bash becomes orphaned when remote terminal killed Message-ID: <20070916182438.GA11396@suncomp1.spk.agilent.com> Mail-Followup-To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I've found this question in the archives, but not the answer. I login to a machine running Cygwin (call it mypc) from one running Linux with this command: xterm -e ssh mypc When I close the xterm on the Linux machine, the login bash process on the Cygwin machine becomes an orphan instead of terminating. Is there a way to have the bash process terminate instead? The reason this is a problem, or rather an annoyance, is that from this bash I run a simple terminal emulator program that copies everything it gets from the tty to a serial port and from the serial port to the tty. Once started, there is no way to end the program other than to send it a signal. I can do this from another ssh login session, but it would be a lot more convenient to just close the xterm. Regards, Gary -- 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/