X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_05,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: problem with sshd Date: Wed, 22 Dec 2010 10:41:14 +0100 Lines: 14 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/3.0.4 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 * 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. That is (or was) an old problem as far as I remember. Search the mailing list archives to see if it is supposed to be fixed or a workaround is available. Maybe someone else here remembers more than me... Thorsten -- 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