Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sun, 18 Mar 2001 20:36:34 +0300
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin-developers AT cygwin DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <437795639.20010318203634@logos-m.ru>
To: Christopher Faylor <cgf AT redhat DOT com>
CC: cygwin-developers AT cygwin DOT com
Subject: Re: Outstanding issues with current DLL?
In-reply-To: <20010318121519.F12880@redhat.com>
References: <20010307213711 DOT E32721 AT redhat DOT com> <3AA79E39 DOT BC915295 AT yahoo DOT com>
 <20010308125701 DOT A4371 AT redhat DOT com> <3AA7CCBA DOT E84FD16E AT yahoo DOT com>
 <20010308133552 DOT A878 AT redhat DOT com> <3AA7E05A DOT BF9F2535 AT yahoo DOT com>
 <20010310184508 DOT A16745 AT redhat DOT com> <3AAFF6E9 DOT DFBF2C8 AT yahoo DOT com>
 <20010317180414 DOT A22971 AT redhat DOT com> <115297467 DOT 20010318180906 AT logos-m DOT ru>
 <20010318121519 DOT F12880 AT redhat DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Sunday, 18 March, 2001 Christopher Faylor cgf AT redhat DOT com wrote:

CF> On Sun, Mar 18, 2001 at 06:09:06PM +0300, Egor Duda wrote:
>>Sunday, 18 March, 2001 Christopher Faylor cgf AT redhat DOT com wrote:
>>
>>CF> On Wed, Mar 14, 2001 at 05:55:37PM -0500, Earnie Boyd wrote:
>>>>This problem doesn't exist in the 2001-Mar-12 snapshot.  However, I do
>>>>have an occasional lockup on exit.  The startup of the command window is
>>>>much faster, I had more that fifty windows open in less than 30 seconds
>>>>just by clicking on the 
>>>>Office shortcut icon.
>>
>>CF> The only lockup that I saw was when I tried to close the window using
>>CF> the X in the upper right corner.  When this happens, cygwin seems to
>>CF> be stuck in a "wait for input from fd 0" loop.
>>
>>i   see   it   too.  when  i start bash via rxvt and then type 'ps -l'
>>bash  it prints that rxvt and bash have different pgid's. so when rxvt
>>receives WM_CLOSE message and tries to exit, it doesn't send SIGHUP to
>>bash.  so  bash  doesn't see that signal_arrived, and continue to wait
>>for input.

CF> Well, bash and ps should have different process groups.

yes. they should. but i wonder whether rxvt and bash should have equal
process groups or not?

CF>   I'm  surprised  that  rxvt doesn't send something to its running
CF> processes when it gets a SIGHUP.

CF> Is rxvt ignoring the SIGHUP?  Does anyone know?  I would think that it
CF> would do *something* on receiving this.

no, it doesn't ignore SIGHUP.  what  it  doesn't do is that it doesn't
propagate  SIGHUP  to it's children. either when closed via 'X' button
or via 'kill -HUP <rxvt_pid>'

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19