X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.1 required=5.0	tests=AWL,BAYES_05,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20101222185024.GA4970@jethro.local.lan>
References: <AANLkTinOHVgUQZ=UtAm7Pw4vxCiww7SAR4K1-LVYNkhz AT mail DOT gmail DOT com> <iesh41$6ha$1 AT dough DOT gmane DOT org> <AANLkTimDhgQutVsjAFJS_zfJPusMjxpjC0of1vPJa9Dh AT mail DOT gmail DOT com> <20101222185024 DOT GA4970 AT jethro DOT local DOT lan>
From: Vasya Pupkin <cygwin AT bsrealm DOT net>
Date: Wed, 22 Dec 2010 22:02:00 +0300
Message-ID: <AANLkTi=v8zmjt3utQSH9+MGwQ=983Zp=O2+rgEq1PLh0@mail.gmail.com>
Subject: Re: problem with sshd
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Wed, Dec 22, 2010 at 9:50 PM, David Sastre <d DOT sastre DOT medina AT gmail DOT com> wrote:
>> >> I have a problem running cygwin sshd. I often end up with a lot of
>> >> bash processes running and eating memory while there are no single
>> >> active ssh session. It happens when either connection lost or user
>> >> closes connection without logging out, sshd process dies but bash
>> >> remains in memory forever. Is it possible to prevent this? In all real
>> >> unix environments this never happen, bash always dies when parent sshd
>> >> exits.
>
> You might want to enable TCPKeepAlive. It could, at a very least,
> prevent disconnections without explicit user interaction.

It's enabled. When sshd not receiving keepalives (network issue or
user closed terminal), it dies (which is good) and leaves bash process
running forever (which is not good).

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