Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Fri, 21 Mar 2003 11:57:54 +0100 (CET)
From:	Pavel Tsekov <ptsekov AT gmx DOT net>
X-X-Sender:	ptsekov AT moria DOT atlanticsky DOT com
To:	Tihomir Ganev <jackripper2600 AT yahoo DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: midnight commander start new bash proccess after exit
In-Reply-To:	<Pine.LNX.4.44.0303211020001.18259-100000@moria.atlanticsky.com>
Message-ID:	<Pine.LNX.4.44.0303211156570.19831-100000@moria.atlanticsky.com>
MIME-Version:	1.0

On Fri, 21 Mar 2003, Pavel Tsekov wrote:

> On Thu, 20 Mar 2003, Tihomir Ganev wrote:
> 
> > Hi all.
> > The problem is that after start mc(midnight commander)
> > and when i
> > exit from it.When i exit new bash shell is start.
> > So when i start and quit 5 times MC in memory reside 6
> > bash
> > proccess.
> 
> This is known issue - I'm aware of it an plan to debug it in the 
> weekend.
> 
> MC doesn't actually start a new shell on exit, but starts the subshell 
> on startup and for some reason it fails to control it properly, so the 
> subshell never dies.
> 
> To fix you problem temorarily start mc like that:
> 
> mc -u
> 
> >From mc --help output:
> -u, --nosubshell       Disables subshell support
> 
> This way MC won't leave any subshells around.

Or better upgrade to mc-4.6.0-2. Should be available on mirrors in several 
hours.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -