X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Robert Pendell <shinji+gmane AT elite-systems DOT org>
Subject:	Re: Bash.exe stays open after Putty is closed
Date:	Sun, 06 Apr 2008 00:16:41 -0400
Lines:	51
Message-ID:	<ft9it0$dse$2@ger.gmane.org>
References:	<47F6B29F DOT 6020904 AT gmail DOT com> <20080405093513 DOT GT5532 AT calimero DOT vinschen DOT de> <b609cb3b0804050639k7de6a062s102b098d9f7e55db AT mail DOT gmail DOT com> <ft8ao6$bjp$1 AT ger DOT gmane DOT org> <b609cb3b0804050958r553d468do215278855f7df5fa AT mail DOT gmail DOT com> <ft8bvu$fut$1 AT ger DOT gmane DOT org> <b609cb3b0804051037o390136adh411b2d6b6f48cfd5 AT mail DOT gmail DOT com>
Mime-Version:	1.0
User-Agent:	Thunderbird 2.0.0.12 (Windows/20080213)
In-Reply-To:	<b609cb3b0804051037o390136adh411b2d6b6f48cfd5@mail.gmail.com>
X-Antivirus:	avast! (VPS 080404-0, 04/04/2008), Outbound message
X-Antivirus-Status:	Clean
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

NightStrike wrote:
| On 4/5/08, Andrew DeFaria <Andrew AT defaria DOT com> wrote:
| [snip lots of useless arguing]
|
| Look, use whatever you want, I don't really care.  If you like
| cygwin's ssh, wonderful!  I don't.  Putty provides me the flexibility
| I need to access many ssh features on a regular basis for the things
| that I do, and is 3 clicks away from downloading/running on any system
| I use that it's never touched before.  cygwin ssh doesn't, and isn't.
| cygwin ssh works great for you and gives you consistency accross many
| systems and fits the requirements that you have for an ssh client.
| Different strokes, different folks.
|
| My intent on answering you was to show you that there are other
| options out there.  Because a person chooses to use putty or cygwin
| ssh doesn't really matter.  My question at the end, "Why NOT use it?"
| was rhetorical to show that it's silly to expect that any one program
| is going to be perfect for every single user, as was implied by your
| question "Why use putty instead of ssh?"
|
| The takeaway is that if bash isn't handling a SIGHUP properly (As
| Paul-Kenji pointed out), then that is an issue that can't be ignored
| by saying "just use cygwin ssh".
|

When you close putty using an Alt+F4 or use the close button then a
SIGHUP isn't always sent.  The server doesn't know that the session was
terminated and may keep it going.  Usually you will need to sign back in
and send a kill -HUP signal to the parent (shell) process.  This
behavior can be observed on a NetBSD server that I remote login to
regularly.

- --
Robert Pendell
shinji AT elite-systems DOT org

"A perfect world is one of chaos."

Thawte Web of Trust Notary
CAcert Assurer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH+E6ps1pR2j1qW+sRAvOAAJ0c5k8dkmSk9NgVlsSZHiLUcOszKQCfRJ13
EjfiFFVkykkHkICThfu7vB8=
=KJhl
-----END PGP SIGNATURE-----


--
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/

- Raw text -