X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
Date: Wed, 22 Dec 2010 19:50:24 +0100
From: David Sastre <d DOT sastre DOT medina AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: problem with sshd
Message-ID: <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>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/"
Content-Disposition: inline
In-Reply-To: <AANLkTimDhgQutVsjAFJS_zfJPusMjxpjC0of1vPJa9Dh@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
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

--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 22, 2010 at 01:17:11PM +0300, Vasya Pupkin wrote:
> On Wed, Dec 22, 2010 at 12:41 PM, Thorsten Kampe
> <thorsten AT XXXXXXXXXXXXXXX> wrote:
http://cygwin.com/acronyms/#PCYMTNQREAIYR
> > * Vasya Pupkin (Wed, 22 Dec 2010 09:26:29 +0300)
> >> 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.=20

$ grep -i keepalive /etc/ssh*config
/etc/ssh_config:TCPKeepAlive yes
/etc/sshd_config:TCPKeepAlive yes

Despite the man pages for ssh_config and sshd_config stating that it
is enabled by default, I had to explicity declare it to prevent ssh=20
connections _from_ a cygwin box to the outside from dying.
This was a while back, though.

Regards.

--=20
Huella de clave primaria: 0FDA C36F F110 54F4 D42B  D0EB 617D 396C 448B 31EB

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk0SSHAACgkQYX05bESLMevwCwCfUKsI+cmDOTdrFSRjSrMbJHKa
xBUAnj+b2OyMGMkWbjET2xIWk2aaNp74
=ErfB
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--