X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <5400a0100712011128o3ac8ff9dne9af8fa1a38ec416@mail.gmail.com> Date: Sat, 1 Dec 2007 20:28:30 +0100 From: "Piotr Kaczorowski" To: "paherbst AT gmail DOT com" Subject: Re: closing SSH session leaves a zombie bash process Cc: corinna-cygwin AT cygwin DOT com, cygwin AT cygwin DOT com In-Reply-To: <2f9457700711301146g6c49e78cscd4aa2bc3c8caa51@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5400a0100711301109m1c64bb19ve53244b0388e31cd AT mail DOT gmail DOT com> <2f9457700711301146g6c49e78cscd4aa2bc3c8caa51 AT mail DOT gmail DOT com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Curious.. I found that if you set shell in /etc/passwd as /bin/cmd.exe (after cp /cygdrive/c/WINDOWS/system32/cmd.exe /bin/cmd.exe), after ssh login and exit by ctrl-F4, CMD is not leaved as zombie process. It's only occurs when shell is cygwin process (/bin/bash or /bin/zsh). 2007/11/30, paherbst AT gmail DOT com : > i never found a solution. i've just been making sure i type exit when > using a shell, or if i'm just tunneling i dont invoke a shell so i > dont have the problem. > > i haven't tried lately to see if any updates have fixed it. > > but if you find any fixes or anything i'd be curious to know what they > are. and if i get around to looking into it again i'll let you know > what i find. or i'll post on the list again. > > thanks, > patrick > > On 11/30/07, Piotr Kaczorowski wrote: > > Hello, > > > > > > Have you found solution for bash process zombies? I have the same > > unbearable problem... > > > > > > best regards, > > Peter > > > -- 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/