X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=BAYES_40,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: References: From: Vasya Pupkin Date: Wed, 22 Dec 2010 13:17:11 +0300 Message-ID: Subject: Re: problem with sshd To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Dec 22, 2010 at 12:41 PM, Thorsten Kampe wrote: > * 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... I searched and found only one message describing this problem which was left without answer... -- 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