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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Rolf Campbell <Endlisnis AT mailc DOT net>
Subject:	Re: Recent snapshots and bash/stopping processes
Date:	Mon, 06 Oct 2003 11:56:13 -0400
Lines:	59
Message-ID:	<bls3at$va1$1@sea.gmane.org>
References:	<blrsim$f5i$1 AT sea DOT gmane DOT org> <20031006144920 DOT GH29063 AT cygbert DOT vinschen DOT de> <bls1km$r5e$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 56 DOT 0310061129320 DOT 15176 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2
X-Accept-Language:	en-us, en
In-Reply-To:	<Pine.GSO.4.56.0310061129320.15176@slinky.cs.nyu.edu>

Igor Pechtchanski wrote:

> On Mon, 6 Oct 2003, Rolf Campbell wrote:
> 
> 
>>Corinna Vinschen wrote:
>>
>>>On Mon, Oct 06, 2003 at 10:00:53AM -0400, Rolf Campbell wrote:
>>>
>>>
>>>>Open one window (rxvt):
>>>>$ sleep 1000
>>>>
>>>>Open a seperate window (rxvt):
>>>>$ ps
>>>>     PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
>>>>    1716       1    1716       1716  con 11643 18:57:52 /usr/bin/rxvt
>>>>    1636    1716    1636       1724    0 11643 18:57:52 /usr/bin/bash
>>>>    1832       1    1832       1832  con 11643 18:59:13 /usr/bin/rxvt
>>>>    2072       1    2072       2072  con 11643 09:35:13 /usr/bin/rxvt
>>>>    2320    2072    2320       2260    2 11643 09:35:16 /usr/bin/bash
>>>>    2360       1    2360       2360  con 11643 09:50:50 /usr/bin/rxvt
>>>>    1844    2360    1844       2404    3 11643 09:50:53 /usr/bin/bash
>>>>    2448    2320    2448       2460    2 11643 09:51:07 /usr/bin/sleep
>>>>    2284    1844    2284       2452    3 11643 09:51:10 /usr/bin/ps
>>>>$ kill -STOP 2448
>>>>$
>>>>
>>>>Look back at first window:
>>>>$ sleep 1000
>>>>
>>>>[1]+  Stopped                 sleep 1000
>>>>$
>>>>
>>>>This has only started happending with recent cygwin versions, I'm
>>>>running Oct2 right now.
>>>
>>>Erm... and what's wrong with this?  It's the same as on Linux.
>>
>>Well, if this is design intent, then that's fine.  But, on older
>>cygwins, it used to just stop the process (the parent of the stopped
>>process (bash) did nothing).  It seems a little awkward to me at least,
>>if I stop/start a process, then I end up with both bash & that process
>>running at the same time, in the same console.
> Rolf,
> 
> The last sentence doesn't make sense.  If you're complaining about the
> notification, put a "set +b" (or "set +o notify") in your .bashrc.
> 	Igor

I'm not complaining about the notification, I'm complaining about the 
fact that bash resumes it's interactivity when one of it's children 
processes receive a stop signal (that it didn't generate).

/home/rcampbell> set +b
/home/rcampbell> sleep 100

[1]+  Stopped                 sleep 100



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

- Raw text -